I believe sites using the popular babelJS transpiler break rendering in Chrome Canary
Reported by
christia...@gmail.com,
Jul 21 2017
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_11_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/59.0.3071.115 Safari/537.36 Steps to reproduce the problem: 1. Go to a site using babel: https://babeljs.io/, https://www.nfl.com/super-bowl, https://www.airbnb.com/ 2. You should see initial HTML render, then as JS loads the page will turn white. 3. There are no JS errors, I haven't been able to identify the root cause What is the expected behavior? These pages should render HTML/CSS, but no images, type, divs are visible after JS loads. What went wrong? I'm guessing there's a collision with a babel ES2017 function that is now native in Chromium. With no JS error feedback it's difficult to tell but that's where I would start. Did this work before? N/A Chrome version: 61.0.3162.0 Channel: canary OS Version: OS X 10.11.6 Flash Version: Shockwave Flash 26.0 r0
,
Jul 21 2017
@christian.harden -- Thanks for posting the issue. Could you please provide the screencast of the expected behavior. This would help us in triaging the issue further. Thanks in advance.
,
Jul 24 2017
I'm seeing this issue in Chrome 61.0.3159.5 (current dev channel release). Another example site that it happens on is https://my.gov.au/LoginServices/main/login. As per @christian.harden, I see an initial flash of the HTML and then the page turns white, with no obvious console errors. The elements panel in DevTools shows that the HTML is there, it is just not painting correctly.
,
Jul 24 2017
Another example site is https://marketplace.atlassian.com/
,
Jul 25 2017
pnangunoori@ Please bisect, if reproducible this is an RB.
,
Jul 26 2017
URGENT - PTAL. Your bug is labelled as Stable ReleaseBlock, pls make sure to land the fix and get it merged into the M61 branch #3163 ASAP to have enough baking time in Beta before Stable promotion. Thank you! Know that this issue shouldn't block the release? Remove the ReleaseBlock-Stable label.
,
Jul 26 2017
The behavior seems similar to the one caused by a duplicated <body> element. Normally it can't occur, but I've encountered a few cases when js code caused Chrome to do it.
,
Jul 26 2017
For what it's worth, I just upgraded (dev channel) from 61.0.3159.5 to 61.0.3163.13; and I am no longer seeing the problem on the sites I previously mentioned (https://my.gov.au/LoginServices/main/login & https://marketplace.atlassian.com/). So (for me at least), it looks like the issue has been resolved.
,
Jul 27 2017
This is no longer an issue for me looking at these websites in Canary Version 62.0.3167.0
,
Jul 27 2017
christian.harden@, thank you for the update! |
||||
►
Sign in to add a comment |
||||
Comment 1 by nyerramilli@chromium.org
, Jul 21 2017