Issue metadata
Sign in to add a comment
|
Initial scale of web page incorrect
Reported by
lbehrman...@gmail.com,
Dec 13 2017
|
||||||||||||||||||||
Issue descriptionDevice name:Samsung Galaxy S7 From "Settings > About Chrome" Application version:Chrome 63.0.3239.83 Operating system: Android 7.0.0; SM-G930V Build/NRD90M URLs (if applicable): https://www.streamlight.com Steps to reproduce: (1)Patch Chrome to current (2)Launch Chrome and go to streamlight.com (3)Page should load at 100%, appears to be somewhere around 110%. (4)Uninstall the update, page loads properly. Page loads properly in other browsers installed on phone. Expected result: Page should load at 100% width. Actual result: Appears to be loading somewhere around 110%.
,
Dec 14 2017
Tested the issue in Android and able to reproduce the issue. Steps Followed: 1. Launched the Chrome Browser. 2. Navigated to the URL: https://www.streamlight.com 3. Observed that page is displayed as zoomed in. Chrome versions tested: 61.0.3161.4, 63.0.3239.83(Stable), 65.0.3292.0(Canary) OS: Android 8.0.0 Android Devices: Pixel XL Build/OPR1.170623 Using the per-revision bisect providing the bisect results, Good build: 61.0.3161.4 (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 From the CL above, assigning the issue to the owner concerned. @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/794575 Note: This issue is not observed in Desktop.
,
Dec 14 2017
This is directly related to discussions in https://bugzilla.mozilla.org/show_bug.cgi?id=1123938#c38 and https://github.com/bokand/bokand.github.io/issues/3. The page works correctly in Firefox but there's no interop here yet so this isn't necessarily a "bug" in Chrome. The page is setting an explicit width that's wider than the device width - On my Nexus 6 the container element (with class `mainContent`) has `width: 494px` while the screen is 412px. This happens from JS so without a reduced test case I can't tell why. My guess is that the page adds some extra content during load (I can see a menu flash all the way on the right) which races with our initial scale / layout viewport sizing. I suspect the approach I mention in the links above would fix this (and align us with Firefox and Safari). I'll block this on issue 437303 to keep a list of impacted web pages.
,
Dec 14 2017
Also, changing component to Blink>Scroll since it's zoom related.
,
Jan 4 2018
,
Jan 11 2018
,
Jan 25 2018
Assigning it to myself to make sure that it has an owner.
,
Nov 16
What is the status of this issue? The problem seems to hac=ve worsened with the latest version of chrome on Android devices. Am now at 69.0.3497.100
,
Nov 16
And when I say worsened I mean that the double tap does rescale correctly. This lasts until I try clicking the navigation pulldown on the upper right. At which point the page becomes unusable.
,
Nov 16
I think the "worsened" behavior may be a problem with the page. Using Firefox, while the initial zoom appears correct, clicking the menu dropdown causes the same kind of unusable state on the page.
,
Nov 19
I'm sorry, but the page works as it should in Firefox on my Android phone. I don't see anything coming close to how it's behaving on Chrome. Am at version 62.0.3 of Firefox on my phone. |
|||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||
Comment 1 by pnangunoori@chromium.org
, Dec 14 2017