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

Issue 782440 link

Starred by 1 user

Issue metadata

Status: Available
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: ----
Pri: 2
Type: Bug

Blocking:
issue 781753



Sign in to add a comment

Tab ordering of element with <slot> seems wrong

Project Member Reported by dpa...@chromium.org, Nov 7 2017

Issue description

Minimal example at https://jsfiddle.net/7h07cono/5/.

Given that the <slot> appears before the checkbox, shouldn't the contents of the <slot> be first in the tab order? This is the root cause of   issue 781753  .

Is this expected behavior? If yes, what is the proposed workaround?
 
Components: Blink>Accessibility

Comment 2 by kochi@chromium.org, Nov 8 2017

Components: -Blink>DOM>ShadowDOM -Blink>Accessibility Blink>HTML>Focus
Status: Available (was: Untriaged)
Blocking: 781753
Posting an updated minimal repro since the previous one might not work in all cases (CDN failure). Try https://jsfiddle.net/7h07cono/5/ instead.

Comment 5 by kochi@chromium.org, Nov 16 2017

catmullings@ the blocking  bug 781753  is marked P1 as it was identified as
a regression, but this is P2 - how urgent/severe is this?

Comment 6 by dpa...@chromium.org, Nov 16 2017

@kochi: MD Extension's has not gone through a11y review yet (but it is going through very soon), so whether  issue 781753  is P1 or P2 is not very clear.

It is a regression from the MD Extension's perspective, since it started happening when the <slot> mechanism was introduced at https://cs.chromium.org/chromium/src/chrome/browser/resources/md_extensions/toggle_row.html?l=42.

Comment 7 by dpa...@chromium.org, Jan 17 2018

Description: Show this description
Cc: -catmulli...@chromium.org

Sign in to add a comment