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

Issue 647658 link

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



Sign in to add a comment

Regression : No ripple effect is seen on 'Clear browsing data' button on pressing spacebar in md-history.

Reported by yfulgaon...@etouch.net, Sep 16 2016 
Chrome Version : 55.0.2862.0 (Official Build) d29bb8a29d313a1939b297c45b39560ff22a89cb-refs/heads/master@{#419063} (64-bit)
OS: Mac(10.10.5)(10.11.5), Windows(7,8,8.1,10), Linux(14.04 LTS)

What steps will reproduce the problem?
1. Launch chrome and navigate to chrome://history.
2. Press tab key till focus is seen on 'Clear browsing data', press Space bar key and observe.

Actual : No ripple effect is seen on 'Clear browsing data' button on pressing spacebar.
Expected : Ripple effect should be seen on 'Clear browsing data' button on pressing spacebar.

This is a regression issue broken in ‘M-54’, below is the Manual Regression and will soon update other info. 
Good build: 54.0.2838.0
Bad build: 54.0.2839.0
Expected_ripple_effect.mov
1.8 MB Download
Actual_ripple_effect.mov
3.4 MB Download

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

Owner: calamity@chromium.org
Status: Assigned (was: Unconfirmed)
Using the per-revision bisect providing the bisect results,
Good build: 54.0.2838.0 (Revision: 413929).
Bad build: 54.0.2839.0 (Revision: 414243).

You are probably looking for a change made after 414033 (known good), but no later than 414034 (first known bad).
CHANGELOG URL:
  https://chromium.googlesource.com/chromium/src/+log/021b51644b1424c1d6262087ea3e57a6fdda36ab..3798937bc576f5408b0d8a7b8789320acaeb821b


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

Thank You.

Comment 2 by msrchandra@chromium.org, Sep 19 2016

Labels: hasbisect-per-revison

Comment 3 by calamity@chromium.org, Sep 20 2016

Status: WontFix (was: Assigned)
This is more or less the desired behavior.
►

Sign in to add a comment