Regression : Flickering of contents is seen on navigated page after clicking on video thumbnail.
Reported by
rp...@etouch.net,
Nov 9 2017
|
||||
Issue descriptionVersion: 64.0.3263.0 (32/64-bit)fd1e89557fa78a467061f732a8473fd863a89b1a-refs/heads/master@{#515052} OS: Windows (8,8.1,10),Linux (14.04 LTS),Mac OS X(10.12.6,10.13.2) What steps will reproduce the problem? 1. Launch chrome, navigate to NTP and open devtools. 2. Now press 'Esc' key to open 'Console' drawer and open 'Whats New' from more options iron icon. 3. Now click on video thumbnail and observe contents(Ex. Updates tab) in navigated page(Refer screen cast) Actual: Flickering of contents is seen on navigated page after clicking on video thumbnail Expected: Flickering of contents should not be seen on navigated page after clicking on video thumbnail This is regression issue, broken in ‘M 63’ and will below is the bisect info : Good build: 63.0.3207.0 (Revision: 499830). Bad build: 63.0.3208.0 (Revision: 500160). You are probably looking for a change made after 499931 (known good), but no lat er than 499932 (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/e32943af2683a9aef43ad21fc98fbe4b392a3fb5..ceffb6f0de79979f9fa7024b0ab8b640659bc04a From the CL above, assigning the issue to the concern owner @yhirano- 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. Suspect : https://chromium.googlesource.com/chromium/src/+/ceffb6f0de79979f9fa7024b0ab8b640659bc04a Thanks! Note : Issue is not seen on Windows 7 OS.
,
Nov 9 2017
With response to comment #1: By default chrome://flags/#enable-mojo-loading is set to 'Default' Note : After enabling above flag the issue is reproduced but after disabling it the issue is not reproduced.
,
Nov 9 2017
Is the issue reproducible with Stable (62.*) with chrome://flags/#enable-mojo-loading enabled? Is the issue not reproducible with Stable (62.*) with chrome://flags/#enable-mojo-loading disabled?
,
Nov 9 2017
Not reproducible on Mac OS X w/62.0.3202.89
,
Nov 9 2017
Is the issue observable by navigating to the page (https://developers.google.com/web/updates/2017/10/devtools-release-notes)? If so, can you upload videos for both reproduced / non-reproduced cases?
,
Nov 9 2017
With response to comment #2: Rechecked the above issue using stable build 62.0.3202.92 and the issue is reproducible after enabling flag and not reproducible after disabling the flag.
,
Nov 9 2017
With response to comment #8: URL : https://developers.google.com/web/updates/2017/08/devtools-release-notes Kindly find the attached screen cast for your reference
,
Nov 9 2017
Thank you. If you can reproduce the issue while taking Performance snapshot with screenshots in devtools (maybe you need to navigate to the page directly, instead of clicking the link), can you upload the log?
,
Nov 9 2017
+ksakamoto@, toyoshim@ as this may be related to webfont loading. +addyo@: Addy, do you happen to have any contact information of the site developer? It would by great if I get help from who knows the page's internal structure. Thanks,
,
Nov 9 2017
With response to comment #10: Kindly review attached file
,
Nov 9 2017
Re #12: Thank you, but unfortunately it is virtually empty. Do you have any log containing screen shots and event entries (especially in "Main" section)?
,
Nov 9 2017
With response to comment #13: Please find attached new log.
,
Nov 9 2017
Thank you! Can you see any flickering in the screenshots in the log attached at #14? I cannot, and I guess that is because the page width is too narrow to show "Updates" string. Is that correct?
,
Nov 9 2017
With response to comment #15: No. I can not see flickering in screenshots.
,
Nov 9 2017
Can you upload the log including flickering?
,
Nov 9 2017
With response to comment #17: I tried with browser resize / smaller window but unable to see flickering in screenshot.Kindly refer attached log file. Thank you.
,
Nov 10 2017
I could reproduce this on Mac by disabling locally-installed Roboto font. So this looks like FOUT(*) of Roboto webfont. Perhaps Mojo loading changed the timing of webfont load a bit and affected the ordering of webfont load / layout / paint? I don't think this is a regression we need to fix; it's expected that layout flashes when font is updated. We didn't see it on this page before mojo-loading just by chance. (*) https://www.paulirish.com/2009/fighting-the-font-face-fout/ |
||||
►
Sign in to add a comment |
||||
Comment 1 by yhirano@chromium.org
, Nov 9 2017