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

Issue 648540 link

Starred by 1 user
Status: Duplicate
Merged: issue 645409
Owner:
█ tsergeant@chromium.org
Not on Chrome
Closed: Sep 2016
Cc:
ajha@chromium.org
█ kavvaru@chromium.org
█ brajkumar@chromium.org
█ durga.behera@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Blue header turns to grey on refreshing in emulated view.

Project Member Reported by bj00129...@techmahindra.com, Sep 20 2016 
Version: 55.0.2866.0 Dev, 55.0.2862.3/8818.0.0 (Official Build) dev-channel Mighty
OS: Ubuntu 14.04, Windows, Chrome-OS

What steps will reproduce the problem?
(1)Launch chrome>>Navigate to chrome://history>>Open devtools and emulate>>Now change device to iPhone/iPad>>click on reload icon and Observe blue header

Expected: Blue header should not turn grey on reloading in emulation view
Actual: Instead header turns to grey on refreshing.

This is Regression issue broken in M-55.Will soon update bisect info.

Manual bisect info:
Good build:55.0.2850.0 Dev
Bad build:55.0.2851.0 Dev

Attaching screen-cast for reference.
Actual_Historypage.ogv
1.3 MB View Download
Expected_Historypage.ogv
979 KB View Download

Comment 1 by kavvaru@chromium.org, Sep 20 2016

Labels: hasbisect-per-revision ReleaseBlock-Stable OS-Mac
Owner: tsergeant@chromium.org
Status: Assigned (was: Unconfirmed)
Able to reproduce the issue on Mac 10.11.6 using chrome version 55.0.2866.0

Change Log::
https://chromium.googlesource.com/chromium/src/+log/d4fe03704abb4c3628cddff5c7aa8f82b86b2b21..310a320dfc58f35272e221ba1cad275a6004754d

Possible suspect::
https://chromium.googlesource.com/chromium/src/+/310a320dfc58f35272e221ba1cad275a6004754d

tsergeant@ Could you please look into this issue,else please route this to an appropriate owner.

Adding stable blocker as this is recent regression,please remove if not required.
Thanks,

Comment 2 by tsergeant@chromium.org, Sep 20 2016

Mergedinto: 645409
Status: Duplicate (was: Assigned)
Merging into  issue 645409  since this looks like a different symptom of the same issue.
►

Sign in to add a comment