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

Issue 898067 link

Starred by 1 user
Status: Closed
Owner:
█ jamwalla@chromium.org
Last visit > 30 days ago
Closed: Oct 23
Cc:
nyerramilli@chromium.org
rbasuvula@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression : Blue focus ring is not seen on 'Reset' button of 'zoom' bubble after clicking on it.

Reported by rp...@etouch.net, Oct 23 
Version: 72.0.3588.0 (Official Build)Revision 56533f367ba451d6545ab0045e8e11f288b36326-refs/branch-heads/3588@{#1}(32/64-bit)
OS: Windows (7,8,8.1,10),Linux (14.04 LTS),Mac OS X(10.13.1,10.14.1,10.13.6)

What steps will reproduce the problem?
1. Launch chrome,navigate to NTP and press 'Cmd ++' to open zoom bubble
2. Now click on 'Reset' button on zoom bubble and observe

Actual: Blue focus ring is not seen on 'Reset' button after clicking on it
Expected: Blue focus ring should be seen on 'Reset' button after clicking on it

This is regression issue, broken in ‘M 72’ and will soon update other info :
Good build: 72.0.3582.0 (Revision: 600164)
Bad build : 72.0.3583.0 (Revision: 600616)
Actual_video.mov
1.6 MB View Download
Expected_video.mov
1.2 MB View Download

Comment 1 by rp...@etouch.net, Oct 23

Labels: hasbisect
Owner: jamwalla@chromium.org
Status: Assigned (was: Unconfirmed)
 You are probably looking for a change made after 600080 (known good), but no later than 600114 (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/c4d2bed4bfb1b58b32f78dc5d5fa73ecb5763106..2b7fffb1d398c887e93e8b85a8a98c91744c2269?pretty=fuller&n=50

Suspect : r600107 ?

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

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

Note : 
1. Provided suspect through 'Chromium bisect' script because unable to perform bisect using 'per-revision' bisect script.
2. Tried performing 'per revision' bisect on multiple Windows and Mac machines but unable to perform the same since getting "RuntimeError: We don't have enough builds to bisect." error.
3. Correction in revision nos: Good build: 72.0.3583.0 (Revision: 599848); Bad build : 72.0.3584.0 (Revision: 600163)


Kindly review attached screen cast for same.

Thanks!

Comment 2 by jamwalla@chromium.org, Oct 23

Status: Closed (was: Assigned)
Thanks! Yes, this is a result of my change (crrev/c/1284055), which was a partial revert of an older change (crrev/c/1189044) that introduced the behavior. So this returns the behavior to how it is on Stable, it's not actually a regression.
►

Sign in to add a comment