New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 679278 link

Starred by 1 user

Issue metadata

Status: Fixed
Owner:
Closed: Feb 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression : Unable to see background contents after undocking devtools into a separate window.

Reported by yfulgaon...@etouch.net, Jan 9 2017

Issue description

Chrome Version : 57.0.2976.0 (Official Build) 062d7b445d6d0ebf509fd923ef027a0a3c6818b1-refs/heads/master@{#442165} 32/64 bit
OS : Mac(10.12.1, 10.11.6, 10.12), Windows(7,8,10), Linux(14.04 LTS)

What steps will reproduce the problem?
1. Launch chrome, navigate to chrome://settings and open devtools.
2. Click on ‘Customize and control devtools’ button and select ‘Dock to bottom’.
3. Again click on ‘Customize and control..’ button and select ‘Undock into separate window’.
4. Now drag the devtools window slightly towards RHS (do not close it) and observe the background contents.

Actual : Background contents are seen missing after undocking devtools into a separate window.
Expected : Background contents should be visible after undocking devtools into a separate window.

This is a regression issue broken in ‘M-57’, below is the Manual Regression range and will soon update other info.
Good build : 57.0.2974.0
Bad build : 57.0.2975.0
 
Actual_devtools.mov
8.2 MB Download
Expected_devtools.mov
7.6 MB Download
Note : Above issue is reproducible on any internal (ex. chrome://history) as well as any web page.
Cc: rbasuvula@chromium.org
Labels: hasbisect-per-revision
Owner: pfeldman@chromium.org
Status: Assigned (was: Unconfirmed)
Using the per-revision bisect providing the bisect results,
Good build: 57.0.2974.0 (Revision: 441962).
Bad build: 57.0.2975.0 (Revision: 442120).

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

CHANGE-LOG URL:
---------------------------------------
https://chromium.googlesource.com/chromium/src/+log/da741e202d31526a2bfd713a236899d2b8582f00..51b59b3aa445abf8ed7d378d565136b602d1726b


From the CL above, assigning the issue to the concern owner

@pfeldman: 
------------------
Could you please look into the issue, pardon me if it has nothing to do with your changes and if possible please assign it to concern owner.

Review-Url:https://codereview.chromium.org/2611843010

Note: Able to reproduce the issue on Win 10.0,Ubuntu 14.04 & Mac10.12.2.
Labels: ReleaseBlock-Stable
adding RB-Stable, please change if required.

Comment 4 by ajha@chromium.org, Jan 16 2017

Cc: ajha@chromium.org
Labels: -ReleaseBlock-Stable Needs-Feedback
This seems to be working fine on the latest canary(57.0.2983.0) of Windows-10 as per the test steps from C#1.

yfulgaonkar@: Please check this on the latest and confirm if the issue is still seen there as well?

Comment 5 by ajha@chromium.org, Jan 16 2017

Note: I was able to reproduce the issue on the reported version: 57.0.2976.0 on Windows-10.
Status: Fixed (was: Assigned)
Labels: -Needs-Feedback
With response to comment #4

Retested above issue in latest Canary (58.0.3012.0) build on Windows 10 and Mac machines, and issue is fixed now. It is working as intended.
Thank you!

Sign in to add a comment