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

Issue 624730 link

Starred by 2 users
Status: Archived
Owner:
█ tsergeant@chromium.org
Not on Chrome
Closed: Jul 2016
Cc:
ajha@chromium.org
█ kavvaru@chromium.org
█ durga.behera@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 3
Type: Bug



Sign in to add a comment

Non-Regression: Blank chrome://settings/clearBrowserData page is seen when chrome://history page is emulated in devtools.

Project Member Reported by bj00129...@techmahindra.com, Jun 30 2016 
Version:53.0.2782.6/8523.0.0 (Official Build) dev-channel Daisy,Peppy and Paine.
OS:Chrome-OS.

Pre-condition: Enable Material Design history flag from chrome://flags.

What steps will reproduce the problem?
(1)Launch chrome>> Navigate to chrome://history page>> Open devtools and click on toggle device toolbar button.
(2)Now click on clear browsing data button in history page and observe.

Expected:Blank page should not be seen.
Actual:Instead blank chrome://settings/clearBrowserData page is seen.

This is a Non Regression issue as it is also seen in 51.0.2704.103 stable daisy.

This issue is not seen in Linux and Windows.
Actual.webm
1.2 MB View Download

Comment 1 by brajkumar@chromium.org, Jun 30 2016

Components: UI>Browser>History
Status: Untriaged (was: Unconfirmed)
Able to reproduce the issue on Chrome-OS (Peppy) M53-53.0.2782.6/8523.0.0 Dev-Channel. Since this is a non-regression issue marking it as untriaged.
Project Member

Comment 2 by sheriffbot@chromium.org, Jul 1 2016

Labels: -M-53 M-54 MovedFrom-53
Moving this nonessential bug to the next milestone.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Comment 3 by tsergeant@chromium.org, Jul 12 2016

Labels: -Pri-2 Proj-MaterialDesign-WebUI Pri-3
Owner: tsergeant@chromium.org
Status: Assigned (was: Untriaged)
This is very minor, but I think I will end up fixing this as part of a related change.

Comment 4 by tsergeant@chromium.org, Jul 18 2016

Status: Fixed (was: Assigned)
This was fixed by R404952.

Comment 5 by dchan@google.com, Mar 4 2017

Labels: VerifyIn-58

Comment 6 by dchan@google.com, Apr 17 2017

Labels: VerifyIn-59

Comment 7 by dchan@google.com, May 30 2017

Labels: VerifyIn-60

Comment 8 by dchan@chromium.org, Aug 1 2017

Labels: VerifyIn-61

Comment 9 by dchan@chromium.org, Oct 14 2017

Status: Archived (was: Fixed)
►

Sign in to add a comment