Luke Warlow

I think some of these questions might need use cases and existing example research to answer fully.

Tentatively removing agenda+ please re-add if this needs further discussion.

I think swapping range for slider makes sense for each of them. Perhaps slider-track-segment to be more explicit. Fwiw slider naming comes I think from the aria role(among other things).

We should also update the structure to match CSS's see https://drafts.csswg.org/css-forms/#slider-pseudos Namely the ticks and thumbs should be siblings of track NOT children.

Waiting for HTML spec changes based on some feedback I and others have given. Once they've been merged I'll continue with this.

I don't seem to have posted a link already so for easy of navigation, the ~~positive~~ neutral standards position can be found at https://github.com/WebKit/standards-positions/issues/215

Apologies for that massive oversight! Completely accidental.

> Will this API allow elements to be dismissed when the user presses the back button on Mobile Safari? There's no specific handling for iOS in this PR (or either...

Apologies for the delay in getting back to this and thanks for the review @aprotyas hopefully address all the feedback that can be. Let me know if there's anything else...

reading-flow (reading-order-items) is relevant to the focusgroup idea imo. It will fall into the same trap that tabbing does today if you use flex and change ordering? Unless focusgroup just...