HTML5 canvas gets enlarged when 'Force enable zoom' was checked
Reported by
ritter....@gmail.com,
Apr 24 2018
|
|||
Issue descriptionExample URL: https://spayevent.com/quiz Steps to reproduce the problem: 1. Make sure 'Force enable zoom' was unchecked. 2. Fetch 'https://spayevent.com/quiz' 3. Observe if the page was correctly loaded. 4. Check 'Force enable zoom'. 5. Reload the page. 6. Observe if the page got enlarged. What is the expected behavior? The page scale must not be changed. What went wrong? With 'Force enable zoom' checked, the specified page which consists of HTML5 canvas gets enlarged as the <body> element gets larger width and height values than those with 'Force enable zoom' unchecked. Does it occur on multiple sites: N/A Is it a problem with a plugin? No Did this work before? Yes http://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Android/488003/ Does this work in other browsers? N/A Chrome version: 61.0.3162.0 Channel: n/a OS Version: 8.1.0 Flash Version: From binary searches by myself with chromium, the problem didn't happen until http://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Android/488003/. But, from on http://commondatastorage.googleapis.com/chromium-browser-snapshots/index.html?prefix=Android/488022/, the problem started to happen. Here's the logs between 488003 (e586721) and 488022 (9474c16). https://chromium.googlesource.com/chromium/src/+log/9474c16947c9c4353cea7b37e1d11aa222c51ea3 I can't figure out which commit caused the problem.
,
Apr 25 2018
Tested the issue in Android and able to reproduce the issue. Steps Followed: 1. Launch Chrome. 2. Navigate to any URL - https://spayevent.com/quiz 3. Wait till the page loads and the content of the page seems to be normal. 4. From Chrome Settings >> Accessibility >> Enable ‘Force Zoom’. 5. Navigate to any URL - https://spayevent.com/quiz 6. Observed that enlarged screen is seen and user is not able to zoom in or zoom out of the screen and site is not in a working condition. Chrome versions tested: 66.0.3359.126(Stable), 68.0.3405.0(Canary) OS: Android 8.1.0 Android Devices: Pixel 2 Using the per-revision bisect providing the bisect results, Good Build - 61.0.3161.0 (487694) Bad Build - 61.0.3162.0 (488073) You are looking for a change made after 488017(GOOD), but before 488018(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/+/6933fe8a1b1d14e0d36a69cb27ef026217595d95 @bokan: Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to owner concerned. Please navigate to below link for log's and video-- go/chrome-androidlogs/836260 Note: 1. This issue is not observed in Desktop. 2. This issue is not observed in FireFox mobile version. Thanks!
,
Apr 25 2018
Issue 836020 has been merged into this issue.
,
Jun 4 2018
Dear Bokan, Can I know any progresses of this issue? I'd like to know if there's a patch to fix this issue. Thank you in advance.
,
Jun 4 2018
Sorry, I haven't had time to look into it yet.
,
Nov 15
Dear Bokan, Any updates on this? I'd like to know if there's a patch to fix this issue. Thank you in advance.
,
Nov 15
No, sorry, unfortunately this is fairly low priority so I'm unlikely to get to it anytime soon. Users can always uncheck that option. |
|||
►
Sign in to add a comment |
|||
Comment 1 by pnangunoori@chromium.org
, Apr 25 2018Labels: Needs-triage-Mobile