New issue
Advanced search Search tips

Issue 919162 link

Starred by 1 user
Status: Assigned
Owner:
sahel@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 1
Type: Bug

Blocking:
issue 919160



Sign in to add a comment

Unfocusable elements can't be reached using spatial-navigation

Project Member Reported by bokan@chromium.org, Jan 4 
Chrome Version       : 73.0.3642.0

This is particularly problematic on mobile pages as they don't typically need focus due to not having a keyboard.

e.g: See the "Install App" banner or up/down vote buttons on mobile reddit.

See: https://docs.google.com/document/d/16FO36U0TIImrc5bw39ftJw6GB93NS51ODoArZbKAMSI/edit#heading=h.4h0c87wka4lz

We probably want some heuristic other than focusable to determine what should qualify as being "eligable" for spatial navigation.

Comment 1 by bokan@chromium.org, Jan 4

Blockedon: 919158
Since spat nav works by moving focus around today - I don't think we can change this until spat nav moves something other than focus so lets block on that.

Comment 2 by bokan@chromium.org, Jan 4

Blockedon: 919160

Comment 3 by bokan@chromium.org, Jan 10

Blockedon: 920818

Comment 4 by bokan@chromium.org, Jan 10

Blockedon: -920818

Comment 5 by bokan@chromium.org, Jan 10

Blocking: 919160

Comment 6 by bokan@chromium.org, Jan 10

Blockedon: -919160

Comment 7 by bokan@chromium.org, Jan 14

Blockedon: -919158
Having taken a closer look at spat-nav, it looks like this doesn't actually need to block on issue 919158. In Element::SupportsSpatialNavigationFocus, spat nav already looks at more than just focusable elements. We can probably just expand this to touchable things. (though this needs to investigate the best way to do that and confirm that would fix cases like mobile reddit)
►

Sign in to add a comment