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

Issue 712110 link

Starred by 1 user
Status: Fixed
Owner:
einbinder@chromium.org
Closed: May 2017
Cc:
nyerramilli@chromium.org
█ msrchandra@chromium.org
█ ranjitkan@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 1
Type: Bug-Regression



Sign in to add a comment

Regression : Focus does not travel to next option after pressing 'Tab' key.

Reported by rp...@etouch.net, Apr 17 2017 
Version: 60.0.3073.0 aadb33c433f1cf2eb17e4862215c9857c7e26dd1-refs/heads/master@{#464873}
OS: Windows (7,8,8.1,10),Linux (14.04 LTS),Mac OS X(10.11.6,10.12.1)

What steps will reproduce the problem?
1. Launch chrome, navigate to NTP and open devtools.
2. Now click on empty space besides 'Performance' section (Keep arrow pointer there itself after clicking) and press 'Tab' key to bring focus on 'Customize and control devtools' iron icon.(Please refer video)
3. Now press 'Space bar' key to open 'Customize and control devtools' drop down list and then press 'Esc' key to dismiss it,now again press 'Tab' key and observe focus travel

Actual: Focus does not travel to next option after pressing 'Tab' key
Expected: Focus should travel to next option after pressing 'Tab' key 

This is regression issue, broken in ‘M 59’ and will soon update other info :
Good build:59.0.3065.0
Bad build: 59.0.3066.0
Actual_video.mp4
659 KB View Download
Expected_video.mp4
855 KB View Download

Comment 1 by msrchandra@chromium.org, Apr 17 2017

Labels: hasbisect-per-revision
Owner: einbinder@chromium.org
Status: Assigned (was: Unconfirmed)
Using the per-revision bisect providing the bisect results,
Good build: 59.0.3065.0 (Revision: 462712).
Bad build : 59.0.3066.0 (Revision: 463122).

You are probably looking for a change made after 462716 (known good), but no later than 462717 (first known bad).
CHANGELOG URL:
  https://chromium.googlesource.com/chromium/src/+log/864d4cde3b40817cf6831a4a2e6711a4f94413b9..2944ef043f8df7c39bef5e40ae95c2ad49c232f7

@einbinder: 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 einbinder@chromium.org, Apr 17 2017

Status: Started (was: Assigned)

Comment 3 by einbinder@chromium.org, May 26 2017

Status: Fixed (was: Started)
►

Sign in to add a comment