Issue metadata
Sign in to add a comment
|
Regression:Unnecessary blank space is seen after closing devtools window at "xfinity.com"
Reported by
adha...@etouch.net,
Aug 3 2016
|
||||||||||||||||||||||
Issue descriptionChrome Version: 54.0.2817.0 (Official Build) cd4d5eb8d957a3ce7ccf0fa60243eccd8ba47691-refs/heads/master@{#409416} (32/64-bit) OS:Windows 7(Aero enabled), Linux (14.04 LTS) Test URL:http://www.xfinity.com/ What steps will reproduce the problem? (1)Launch chrome and navigate to the above URL. (2)Scroll down the page and click on the video under 'What is XFINITY® X1?' section. (3)Play the video,Open devtools and click on toggle device toolbar twice. (4)Close devtools window and observe. Actual:Unnecessary blank space is observed after step 4. Expected:No such unnecessary blank space should be seen after step 4. This is a Regression issue broken in M-54,below is the Change log: https://chromium.googlesource.com/chromium/src/+log/54.0.2816.0..54.0.2817.0?pretty=fuller&n=10000 Suspecting:r409131? Good build:54.0.2716.0 Bad build:54.0.2717.0 Note:(1)Unable to perform Flash bisect for above issue as issue is not playing in chromium build. (2)Above issue is not reproducible on Mac,Win 8,10 as it is Win 7 specific issue. Kindly help to re-assign if your change is not the cause for this issue.
,
Aug 3 2016
,
Aug 8 2016
@dgozman: Hey,would you mind providing an update on the above issue ?
,
Aug 8 2016
I cannot reproduce this either, since video is not playing. And this is definitely not r409131 - it was an unrelated rename. I see a lot of these warnings: A Parser-blocking, cross-origin script, <url here>, is invoked via document.write. This may be blocked by the browser if the device has poor network connectivity. Could it be possible they affect the video? Sounds like a bigger problem. @shivanisha: could you please take a look?
,
Aug 11 2016
Unable to reproduce the issue on win8.1 chrome version 54.0.2826.0 - No blank space observed after step 4 adharap@, Could you please recheck in latest canary and update the thread.
,
Aug 15 2016
As per the change log https://chromium.googlesource.com/chromium/src/+log/54.0.2816.0..54.0.2817.0?pretty=fuller&n=10000, there has been no change in doc.write blocking functionality between the 2 versions, so the doc.write blocking warnings are unrelated to this behavior.
,
Aug 18 2016
Just to update the latest behavior of the bug. Issue is still able to reproduce it on Windows-10 using chrome latest canary M54-54.0.2831.0.
,
Aug 22 2016
Note:Above issue is not seen on latest canary version 54.0.2836.0 (Official Build) 5916d5e380c5a9da48673de99d40267507d46f34-refs/heads/master@{#413363}(32/64-bit)
,
Aug 25 2016
Thanks adharap@ for the update. Closing the issue as this no longer reproduces on the latest M-54 as per C#5 and C#8. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by ranjitkan@chromium.org
, Aug 3 2016