Chrome renderer fails when there's a "minimum-scale=1.0" and jQuery imported.
Reported by
danielgi...@gmail.com,
Mar 7 2016
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/48.0.2564.116 Safari/537.36 Steps to reproduce the problem: 1. Create a blank page, with something simple, even one word of text. 2. Import jQuery. 3. Add <meta name="viewport" content="width=device-width, minimum-scale=1.0" /> 4. In the "emulation" section of the Dev tools, choose a mobile device like iPhone 6. 5. Refresh the page. What is the expected behavior? Render the page with the supplied text. What went wrong? The page is blank. Did this work before? N/A Chrome version: 48.0.2564.116 Channel: n/a OS Version: 10.0 Flash Version: This happens by default in Chrome for Android too. The weird thing is - any other minimum-scale value, like 0.999 or 1.001 or 2.0 or 0.5 works. Just 1.0 breaks down.
,
Sep 4 2016
I'm experiencing this too. I'm replacing <meta name="viewport" content="width=device-width, minimum-scale=1.0, maximum-scale=1.0" /> with <meta name="viewport" content="width=device-width, minimum-scale=0.999, maximum-scale=1.0" /> And then it works. But this is a weird hack. I've debugged jQuery a lot, and seems like the creation of test elements are the trigger, when the viewport tag is present. But couldn't put the finger on the exact line that causes this, as the bug is random when you put breakpoints. I'm guessing something that measures an element or otherwise causes a page re-layout, at that point in time, with the 100% viewport constraint, causes the layout process to crash.
,
Sep 4 2017
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot |
||
►
Sign in to add a comment |
||
Comment 1 by danielgi...@gmail.com
, Mar 7 2016