Issue metadata
Sign in to add a comment
|
Background images shifting when using display scaling on windows 10
Reported by
frnkprn...@gmail.com,
Mar 17 2017
|
||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/56.0.2924.87 Safari/537.36 Example URL: https://jsfiddle.net/FrankPrins/p1tvL5yf/ Steps to reproduce the problem: Problem applies to Windows 10 using chrome 56.0.2924.87 (64-bit) 1. On windows 10, go to "settings" -> "display" -> "Change the size of text, and other items on this display"and set the slider to for example 125%. 2. Go to https://jsfiddle.net/FrankPrins/p1tvL5yf/ What is the expected behavior? The expected behavior is that the image displays properly, and doesn't shift based on the display size. Firefox works properly, but ie and edge don't. What went wrong? It seems that the scaling messes the displayal of background images up. Included are 2 snaps. "expected.png" is taken when the display scaling is set at the default, 100%. The other "unexpected.png" is when scaling is set to 125% Does it occur on multiple sites: Yes Is it a problem with a plugin? No Did this work before? No Does this work in other browsers? Yes Chrome version: 56.0.2924.87 Channel: stable OS Version: 10.0 Flash Version:
,
Mar 20 2017
,
Mar 20 2017
Broken in Version 57.0.2987.88 beta (64-bit), fixed in Version 59.0.3033.1 canary SyzyASan. The issue is sprite sheet sub-sampling at various sub-pixel sizes. I would not expect to see this fixed. Need a bisect to figure out when it broke to see if we need to merge something.
,
Mar 20 2017
,
Mar 21 2017
Able to reproduce this issue on Windows 10 with chrome stable #57.0.2987.110 and Canary #59.0.3047.0 Issue Broken in M54. Bisect Info: =========== Good build : 54.0.2807.0 , Revision Range - 407480 Bad build : 54.0.2808.0 , Revision Range - 407658 After executing the per-revision bisect script , i got the following CL's between good and bad build versions =========================================== https://chromium.googlesource.com/chromium/src/+log/96b9ba41a7be9329fd486b973082a068bf7ec07c..23364eecc5d1bb1770f8c22a7c0a320154e3eac7 The suspecting Change Log is : ----------- https://chromium.googlesource.com/chromium/src/+/23364eecc5d1bb1770f8c22a7c0a320154e3eac7 Review-Url: https://codereview.chromium.org/2175693004 robliao@ - Could you please look into this issue, if it's related to your change? if not could you please help us to reassign this issue to the right owner.
,
Mar 21 2017
The blamed changelist reveals the bug because we start paying attention to the DPI settings, but in reality the bug has existed longer. The good news is that this large project is next on my agenda. |
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by dtapu...@chromium.org
, Mar 19 2017