New issue
Advanced search Search tips

Issue 884966 link

Starred by 3 users
Status: Assigned
Owner:
aboxhall@chromium.org
Cc:
aboxhall@chromium.org
dmazz...@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Chrome
Pri: 1
Type: Bug-Regression
Team-Accessibility



Sign in to add a comment

focus() method doesn't give focus ring to target element.

Reported by imamura....@gmail.com, Sep 18 
UserAgent: Mozilla/5.0 (X11; CrOS x86_64 10895.56.0) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/69.0.3497.95 Safari/537.36
Platform: 10895.56.0 (Official Build) beta-channel peppy

Steps to reproduce the problem:
In my test app(Use attached file [focusTest.zip]):
1. Remove focus from buttonA and buttonB.
2. Click buttonA.(It calls document.getElementById("btnB").focus()).

What is the expected behavior?
ButtonB is indicated by a focus ring.

What went wrong?
Any elements isn't indicated by a focus ring.

Did this work before? N/A 

Chrome version: 69.0.3497.95  Channel: stable
OS Version: 10895.56.0
Flash Version: 

On Mac Chrome 68, this issue doesn't reproduce.
On both Chromebook and Mac Chrome 69, this issue reproduces.

This issue reproduces when remove focus from all controls.
This issue doesn't reproduce when change focus from buttonA to buttonB by using focus() method.
focusTest.zip
44.7 KB Download

Comment 1 by nzolghadr@chromium.org, Sep 19

Components: -Blink Blink>Forms>Button
I can see that document.activeElement is set correctly.

Just to add another observation, while I was also playing with the page I could get the following scenario to work:
1. Reload the page.
2. Press tab to select button A as focused and the ring does show up.
3. Now clicking on button A does show ring around button B.

Comment 2 by nzolghadr@chromium.org, Sep 19

Status: Untriaged (was: Unconfirmed)

Comment 3 by tkent@chromium.org, Sep 20

Components: Blink>Accessibility
Owner: aboxhall@chromium.org
I remember aboxhall@ changed this behavior.

Comment 4 by dmazz...@chromium.org, Sep 21

Labels: -Type-Bug -Pri-2 -Via-Wizard-Javascript ReleaseBlock-Beta M-70 Pri-1 Type-Bug-Regression
Status: Assigned (was: Untriaged)
Adding releaseblock just in case. Alice, feel free to remove if this is WAI.

Comment 5 by geo...@google.com, Sep 25 

Friendly ping on this to see if we should keep this as a Beta blocker or if we can move to RBS. Thanks.

Comment 6 by tkent@chromium.org, Oct 1 

 Issue 890186  has been merged into this issue.

Comment 7 by geo...@google.com, Oct 1

Labels: -ReleaseBlock-Beta ReleaseBlock-Stable

Comment 8 by geo...@google.com, Oct 4

Labels: -ReleaseBlock-Stable
[bulk edit] Removing Release Block Stable. Please feel free to reapply label with justification in a comment. Thanks.
►

Sign in to add a comment