Issue metadata
Sign in to add a comment
|
Regression:Text appears blur after performing pinch to zoom on edit page overlay
Reported by
vku...@etouch.net,
Oct 30 2017
|
||||||||||||||||||||||
Issue descriptionChrome Version: 63.0.3239.26(Official build) 4dc4a1fadfb64aefa5850be806dac60336406dd9-refs/branch-heads/3239@{#286} (32/64-bit) OS: Windows 10 Touch device What steps will reproduce the problem? (1)Launch chrome and navigate to twitter.com (2)Navigate to chrome://settings/ > on startup > open a specific page..> use current pages (3)Tap on edit zoom in/out using pinch to zoom and observe Actual: Text appears blur after performing pinch to zoom on edit page overlay. Expected: Text should be properly seen after performing pinch to zoom on edit page overlay. This is a Win 10 touch device specific regression issue broken in 'M63' and below is the bisect info Good build: 63.0.3205.0 Bad Build: 63.0.3206.0 You are probably looking for a change made after 499514 (known good), but no later than 499515 (first known bad). CHANGELOG URL: The script might not always return single CL as suspect as some perf builds might get missing due to failure. https://chromium.googlesource.com/chromium/src/+log/b70fe76b06b21bac5f75bd30a982df398717333e..cd76873d94cd26b7f65d5ddd18663406ec92c1a9 Suspecting: https://chromium.googlesource.com/chromium/src/+/cd76873d94cd26b7f65d5ddd18663406ec92c1a9 Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.
,
Nov 6 2017
@johnme: Gentle ping, request you to please take a look into it. Issue is tagged with a blocker for M63 and is set to be pushed to stable soon. Thanks.!
,
Nov 6 2017
M63 Stable promotion is coming soon and your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and request a merge to M63 ASAP. Thank you.
,
Nov 7 2017
Since John no longer on Chrome team assigning bug to David based on offline Chat for further insights.
,
Nov 8 2017
chaopeng@ says this only occurs on the settings page so this doesn't seem like a blocker to me. Still, we should investigate and fix quickly. The blamed patch seems very unlikely to me to have this effect. Chao, could you double check whether reverting that patch helps? If not, we'll need to do a new bisect to find the culprit.
,
Nov 13 2017
I can't notice a difference when I try this on a Surface Book Pro between Chrome Stable 62.0.3202.89 and Canary 64.0.3267.0. What device were you using? If there really is a clear difference, could you please retry the bisect? I suspect this isn't a regression and maybe the combination of screen resolution and what scale you land on the pinch zoom produces a bad result...
,
Nov 13 2017
,
Nov 17 2017
vkupte@, could you be more specific about what device you were seeing this on? In particular, the screen pixel density might make a difference (you can get that by opening up dev tools - ctrl + shift + i, and typing `window.devicePixelRatio` into the console.
,
Dec 7 2017
vkupte@ are u still seeing this issue?
,
Dec 8 2017
As per comment 8 & 9: Rechecked again and above issue is not reproducible on latest canary version 65.0.3288.0(Official build) on Windows 10 touch device.
,
Dec 14 2017
Thanks, closing as per #10 |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by rbasuvula@chromium.org
, Nov 2 2017