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

Issue 648882 link

Starred by 3 users
Status: WontFix
Owner:
xiaoche...@chromium.org
Closed: Sep 2016
Cc:
nyerramilli@chromium.org
█ ranjitkan@chromium.org
dpa...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression:Content of chrome://settings/clearBrowserData page is not displayed properly after hitting spacebar key.

Reported by vku...@etouch.net, Sep 21 2016 
Chrome Version:	55.0.2867.0 (Official Build)Revision b195fcd2e028db859a382323fad3c6910e3205c4-refs/heads/master@{#419930} (32/64-bit)
OS: Windows(7,8,8.1,10),Mac(10.10.5)(10.11.5),Linux(14.04 LTS)

What steps will reproduce the problem?
(1)Launch chrome and navigate to chrome://history/
(2)Press tab key till focus reaches 'clear browsing data' option
(3)Now press and hold spacebar key till chrome://settings page appears, observe the content of page.

Actual: Content of chrome://settings/clearBrowserData page is not displayed properly after hitting spacebar key.

Expected:  Content of chrome://settings/clearBrowserData page should be properly displayed after hitting spacebar key.

This is a regression issue broken in 'M55' and below is the manual regression range:
Good Build: 55.0.2862.0
Bad Build:  55.0.2863.0
Actual_Settings.mp4
454 KB View Download
Expected_Settings.mp4
351 KB View Download

Comment 1 by msrchandra@chromium.org, Sep 22 2016

Labels: ReleaseBlock-Stable hasbisect-per-revision
Owner: xiaoche...@chromium.org
Status: Assigned (was: Unconfirmed)
Using the per-revision bisect providing the bisect results,
Good build: 55.0.2862.0 (Revision: 419063).
Bad build: 55.0.2863.0 (Revision: 419330).

You are probably looking for a change made after 419066 (known good), but no later than 419067 (first known bad).
CHANGELOG URL:
The script might not always return single CL as suspectas some perf builds might get missing due to failure.
 https://chromium.googlesource.com/chromium/src/+log/56eaf1eac112390d863b0d738ad97d05730d36e2..cd626f11b0ddb8fc655ac2fd808ca3930e3e29cf

From the CL above, assigning the issue to the concern owner --
@xiaochengh -- 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.

Adding RB Label as this is a recent Regression. Please remove if not required.
Thank You.

Comment 2 by xiaoche...@chromium.org, Sep 22 2016 

The CL mentioned in #1 is already reverted by r420023.

I cannot repro the issue with Canary 55.0.2868.0. Could anyone from test team help me verify if the issue is fixed?

Comment 3 by ajha@chromium.org, Sep 28 2016

Status: WontFix (was: Assigned)
I was able to repro this on the reported version: 55.0.2867.0 but this seems to be working fine on the latest canary(55.0.2874.0) on Windows 10.

Closing the issue as this is no longer reproducible.
►

Sign in to add a comment