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

Issue 676760 link

Starred by 5 users
Status: Fixed
Owner:
caseq@chromium.org
Closed: Dec 2016
Cc:
█ hdodda@chromium.org
nyerramilli@chromium.org
pfeldman@chromium.org
dgozman@chromium.org
█ ranjitkan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression : Blank devtools window is seen after undocking devtools into separate window.

Reported by yfulgaon...@etouch.net, Dec 23 2016 
Chrome Version : 57.0.2960.0 (Official Build) 13e0b315a37468b305d5504caab8f3dd3691f3ba-refs/heads/master@{#440547} 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 and open devtools on NTP.
2. Click on ‘Customize and control devtools’ icon and select ‘Undock into separate window’.
3. Click on ‘Customize and control devtools’ and select ‘dock to right’.
4. Again click on ‘Customize and control devtools’ icon and select ‘Undock into separate window’, observe.

Actual : Blank devtools window is seen after undocking devtools into separate window.
Expected : Devtools window should not turn blank after undocking into 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.2951.0
Bad build : 57.0.2952.0
Actual_result.mov
5.0 MB Download
Expected_result.mov
5.4 MB Download

Comment 1 by hdodda@chromium.org, Dec 23 2016

Cc: hdodda@chromium.org
Labels: hasbisect-per-revision ReleaseBlock-Stable
Owner: pfeldman@chromium.org
Status: Assigned (was: Unconfirmed)
Using the per-revision bisect providing the bisect results,
Good build : 57.0.2951.0 (Revision : 438385)
Bad build : 57.0.2952.0 (Revision : 438707)

You are probably looking for a change made after 438415 (known good), but no later than 438416 (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/1a7c8ad0c25e9050ba74d00494590c35a8553735..8ac28391aa13c48a46d1c35bf36e15b1e3c32452

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

@pfeldman - 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.

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

Thanks!

Comment 2 by ranjitkan@chromium.org, Dec 23 2016

Labels: -ReleaseBlock-Stable ReleaseBlock-Beta
Increasing Priority. Please reduce accordingly.

Thanks.!

Comment 3 by anjumani...@gmail.com, Dec 23 2016

love-image-7.jpg
35.9 KB View Download

Comment 4 by ajha@chromium.org, Dec 29 2016

Cc: caseq@chromium.org
Can we get an update on this issue. This is still reproducible on the latest M-57(57.0.2966.0) as tested on Linux Ubuntu 14.04.

Comment 5 by caseq@chromium.org, Dec 29 2016

Cc: dgozman@chromium.org

Comment 7 by caseq@chromium.org, Dec 29 2016

Cc: -caseq@chromium.org pfeldman@chromium.org
Owner: caseq@chromium.org
Status: Fixed (was: Assigned)

Comment 8 by ajha@chromium.org, Jan 3 2017

Labels: TE-Verified-57.0.2970.0 TE-Verified-M57
Verified the fix on the latest canary(57.0.2970.0) on Windows-10, Mac OS 10.12.2 and Linux Ubuntu 14.04. This is working as intended hence adding the verified label.
►

Sign in to add a comment