New issue
Advanced search Search tips

Issue 814325 link

Starred by 1 user
Status: Fixed
Owner:
pfeldman@chromium.org
Closed: Mar 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Navigating to a page with device toolbar open makes part of the screen white

Reported by richard....@hotmail.ca, Feb 21 2018 
UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3350.0 Safari/537.36

Steps to reproduce the problem:
1. Open devtools with device toolbar activated prior to navigating to a different page
2. Navigate to any page, ie. lapresse.ca
3. Notice the white stripes on the right and the bottom of the screen.

What is the expected behavior?
I expect to see the whole webpage without parts missing.

What went wrong?
A counter example would be to load the webpage normally without devtools open. Then open devtools with device toolbar and it works as expected.

It seems to dislike having the devtools already opened prior to navigating to a page.

Did this work before? Yes 

Chrome version: 66.0.3350.0  Channel: canary
OS Version: 10.0
Flash Version: 

It has been going for weeks before I grew tired

Comment 1 by richard....@hotmail.ca, Feb 21 2018

chromebug.PNG
290 KB View Download
devtools-opened-after-navigation.PNG
523 KB View Download

Comment 2 by sindhu.chelamcherla@chromium.org, Feb 21 2018

Labels: Needs-Bisect Needs-Triage-M66

Comment 3 by viswa.karala@chromium.org, Feb 22 2018

Labels: -Pri-2 -Needs-Bisect ReleaseBlock-Stable Triaged-ET M-66 FoundIn-66 Target-66 RegressedIn-66 hasbisect Pri-1
Owner: pfeldman@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on reported version 66.0.3350.0 using Windows-10, hence providing Bisect Info
Note: Issue is not seen on Mac and Linux
Bisect Info:
================
Good build: 66.0.3341.0
Bad build: 66.0.3342.0

You are probably looking for a change made after 534625 (known good), but no later than 534633 (first known bad).

https://chromium.googlesource.com/chromium/src/+log/d7c23f80b5a43d33bfa9c88b785eaccf0338e9bd..4741320d2e6d0a354e22e8aa86079c49c62aa490

Change-Id: I01e1be7fd273dd54f75968f32b2d27889b017dd8
Reviewed-on: https://chromium-review.googlesource.com/902901

@Pavel Feldman: Please confirm the issue and help in re-assigning if it is not related to your change.
Adding ReleaseBlock-Stable as it is seems a receent break, feel free to remove it if not applicable.

Thanks!

Comment 4 by pfeldman@chromium.org, Mar 6 2018 

Can't repro on 67.0.3364.0. Could you give it another try?

Comment 5 by richard....@hotmail.ca, Mar 7 2018 

It would seem that this issue was fixed recently as well!
Don't have the exact version number bu it works again.

Comment 6 by jmukthavaram@chromium.org, Mar 19 2018 

 richard.savoie@,
Can we close this issue as per C#5?Please confirm.

Thanks..!

Comment 7 by richard....@hotmail.ca, Mar 19 2018 

Yes please. This has been fixed.

Comment 8 by pfeldman@chromium.org, Mar 19 2018

Status: Fixed (was: Assigned)
Project Member

Comment 9 by blocker...@chrome-infra-auth.iam.gserviceaccount.com, Mar 19 2018

Labels: Merge-TBD
[Auto-generated comment by a script] We noticed that this issue is targeted for M-66; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-66 label, otherwise remove Merge-TBD label. Thanks.

Comment 10 by abdulsyed@google.com, Mar 20 2018 

pfeldman@, richard.savoie@ - can we please confirm if this issue is happening on M66 Beta, 66.0.3359.33. Branch 3359 will be our stable candidate and I'd like to ensure if this is fixed on that branch. It's unclear when the fix landed and which branch it landed in.
Project Member

Comment 11 by sheriffbot@chromium.org, May 1 2018

Labels: -Merge-TBD
►

Sign in to add a comment