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

Issue 784244 link

Starred by 4 users
Status: Fixed
Owner:
patricia...@chromium.org
Closed: Nov 2017
Cc:
nyerramilli@chromium.org
rbasuvula@chromium.org
patricia...@chromium.org
jlebel@chromium.org
█ msrchandra@chromium.org
█ ranjitkan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Chrome , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression: Focus is not seen while pressing tab key on Avatar Menu.

Reported by aiman.an...@etouch.net, Nov 13 2017 
Chrome Version: 64.0.3266.0 (Official Build)(cohort: 62_89_win)9f1225c70924c5b3312d0571017f855ddaa60a78-refs/heads/master@{#515827}(32/64-bit)

OS:Win(7,8,10), Mac(10.12.6, 10.13.2), Linux(14.04 LTS)

Steps to reproduce:
1. Launch Chrome, click on Avatar icon and press tab.
3. Observe.

Actual Result: Focus is not seen when tab key is pressed.
Expected Result: Focus should be seen when tab key is pressed.

This is regression issue broken in ‘M-64’ and and will soon update the bisect info.

Maunal bisect.
Good Build: 64.0.3264.0 
Bad Build: 64.0.3265.0
Actual Result.mp4
513 KB View Download

Comment 1 by aiman.an...@etouch.net, Nov 13 2017

Labels: hasbisect-per-revision
Owner: patricia...@chromium.org
Status: Assigned (was: Unconfirmed)
Summary: Regression: Focus is not seen while pressing tab key on Avatar Menu. (was: Regression: Focus is not seen when tabg key is pressed on Avatar Menu.)
Using the per-revision bisect providing the bisect results,
Good Build: 64.0.3264.0  (Revision:515410)
Bad Build: 64.0.3265.0 (Revision:515780)

You are probably looking for a change made after 515442 (known good), but no later than 515443 (first known bad).

CHANGE-LOG 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/2e7619405ff3e99d6e24758165d89e307310e1c2..7d840bcd63eaa0b76005bcd4b16a4f6fed0619a1

Suspect: https://chromium.googlesource.com/chromium/src/+/7d840bcd63eaa0b76005bcd4b16a4f6fed0619a1

patricialor: 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.

Thank You!
Expected Result.mp4
730 KB View Download

Comment 2 by patricia...@chromium.org, Nov 13 2017

Cc: jlebel@chromium.org patricia...@chromium.org
 Issue 784235  has been merged into this issue.

Comment 3 by patricia...@chromium.org, Nov 13 2017

Labels: OS-Chrome
Status: Started (was: Assigned)

Comment 4 by patricia...@chromium.org, Nov 14 2017

Status: Fixed (was: Started)
Oops, I never updated the issue number on the CL that fixed this - see https://bugs.chromium.org/p/chromium/issues/detail?id=784235#c3 for the bugdroid post.
►

Sign in to add a comment