|
|
Chromium Code Reviews|
Created:
5 years, 10 months ago by raymes Modified:
5 years, 10 months ago CC:
chromium-reviews, arv+watch_chromium.org, chrome-apps-syd-reviews_chromium.org, majidvp Base URL:
https://chromium.googlesource.com/chromium/src.git@master Target Ref:
refs/pending/heads/master Project:
chromium Visibility:
Public. |
DescriptionAllow mousewheel scrolling to work in print preview on HiDPI devices
Right now, due to crbug.com/455439 mouse wheel scrolling doesn't work in print
preview on HiDPI devices. This hack forces the margins onto separate layers
to work around the bug until it's fixed.
BUG=455439
Committed: https://crrev.com/957b7b651c5fdd8ecfd31d010bde08bc9ac50b38
Cr-Commit-Position: refs/heads/master@{#315898}
Patch Set 1 #
Messages
Total messages: 16 (2 generated)
raymes@chromium.org changed reviewers: + alekseys@chromium.org, rbyers@chromium.org
What about fixing the weird clip? Without fixing that, promoting these to a layer will eat up a lot more GPU memory (each layer was full screen if I recall - when really it should be just the side of the clickable handle you want).
On 2015/02/09 06:36:08, Rick Byers wrote: > What about fixing the weird clip? Without fixing that, promoting these to a > layer will eat up a lot more GPU memory (each layer was full screen if I recall > - when really it should be just the side of the clickable handle you want). sorry - s/side/size/
It looks like the margins get placed on small layers by doing this (at least I think so). Also, it turned out to be very hard to fix the clip properly. Adjusting the length of the margins was easy, but making them disappear at the right time if they were fully obscured was hard. For example, if you scroll and a vertical margin starts to cover the vertical scrollbar then you want to hide it. But hiding it at the right time wasn't easy (if the clickable-padding covers the scrollbar then it interferes with scrolling, but at that point the margin hasn't actually visually obscured the scrollbar). Thanks!
On 2015/02/09 06:51:32, raymes wrote: > It looks like the margins get placed on small layers by doing this (at least I > think so). > > Also, it turned out to be very hard to fix the clip properly. Adjusting the > length of the margins was easy, but making them disappear at the right time if > they were fully obscured was hard. For example, if you scroll and a vertical > margin starts to cover the vertical scrollbar then you want to hide it. But > hiding it at the right time wasn't easy (if the clickable-padding covers the > scrollbar then it interferes with scrolling, but at that point the margin hasn't > actually visually obscured the scrollbar). > > Thanks! Ok, if this is creating small layers (i.e. with 'show composited layer borders' or ideally the 'layers panel' I showed you) then this LGTM.
Hey Rick, I had a closer look and the large layers are still there unfortunately :(. However given that this is not significantly worse than what is existing, I'd like to move forward with this. I spent several hours trying to get rid of the clip rect yesterday but, as I mentioned, it is hard and unfortunately I don't have the time to spend on it right now. I can file it as a separate print preview performance bug if you like. Please let me know if that sounds ok. Thanks!
On 2015/02/09 23:56:34, raymes wrote: > Hey Rick, I had a closer look and the large layers are still there unfortunately > :(. However given that this is not significantly worse than what is existing, > I'd like to move forward with this. I spent several hours trying to get rid of > the clip rect yesterday but, as I mentioned, it is hard and unfortunately I > don't have the time to spend on it right now. I can file it as a separate print > preview performance bug if you like. > > Please let me know if that sounds ok. Thanks! Ok, this should be very temporary anyway. I think Majid has what he needs to fix the chrome bug. The hopefully you can revert this change. LGTM. Sorry for all the trouble.
On 2015/02/10 00:59:26, Rick Byers wrote: > On 2015/02/09 23:56:34, raymes wrote: > > Hey Rick, I had a closer look and the large layers are still there > unfortunately > > :(. However given that this is not significantly worse than what is existing, > > I'd like to move forward with this. I spent several hours trying to get rid of > > the clip rect yesterday but, as I mentioned, it is hard and unfortunately I > > don't have the time to spend on it right now. I can file it as a separate > print > > preview performance bug if you like. > > > > Please let me know if that sounds ok. Thanks! > > Ok, this should be very temporary anyway. I think Majid has what he needs to > fix the chrome bug. The hopefully you can revert this change. LGTM. Sorry for > all the trouble. No problem, thank you for your help!
alekseys: please let me know if this is ok with you :) On Tue Feb 10 2015 at 12:10:18 PM <raymes@chromium.org> wrote: > On 2015/02/10 00:59:26, Rick Byers wrote: > > On 2015/02/09 23:56:34, raymes wrote: > > > Hey Rick, I had a closer look and the large layers are still there > > unfortunately > > > :(. However given that this is not significantly worse than what is > existing, > > > I'd like to move forward with this. I spent several hours trying to get > > rid > of > > > the clip rect yesterday but, as I mentioned, it is hard and > > unfortunately I > > > don't have the time to spend on it right now. I can file it as a > > separate > > print > > > preview performance bug if you like. > > > > > > Please let me know if that sounds ok. Thanks! > > > Ok, this should be very temporary anyway. I think Majid has what he > > needs to > > fix the chrome bug. The hopefully you can revert this change. LGTM. > > Sorry > for > > all the trouble. > > No problem, thank you for your help! > > https://codereview.chromium.org/912433002/ > To unsubscribe from this group and stop receiving emails from it, send an email to chromium-reviews+unsubscribe@chromium.org.
Friendly ping :)
lgtm
The CQ bit was checked by raymes@chromium.org
CQ is trying da patch. Follow status at https://chromium-cq-status.appspot.com/patch-status/912433002/1
Message was sent while issue was closed.
Committed patchset #1 (id:1)
Message was sent while issue was closed.
Patchset 1 (id:??) landed as https://crrev.com/957b7b651c5fdd8ecfd31d010bde08bc9ac50b38 Cr-Commit-Position: refs/heads/master@{#315898} |
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
