Re: [csswg-drafts] [css-overflow-5] Discrete versus navigation scroll marker mode (#12122)

The CSS Working Group just discussed `[css-overflow-5] Discrete versus navigation scroll marker mode`, and agreed to the following:

* `RESOLVED: Add second value to scroll-marker-group as [ tabs | links ]`

<details><summary>The full IRC log of that discussion</summary>
&lt;kbabbitt> flackr: one of the biggest points of feedback we got on scroll marker pseudo<br>
&lt;kbabbitt> ... is that these are used for many different use cases<br>
&lt;kbabbitt> ... not all of which are tabs<br>
&lt;kbabbitt> ... and our use of the tab rules on scroll marker pseudos is not always appropriate<br>
&lt;kbabbitt> ... I'm proposing that we have a mode switch property<br>
&lt;kbabbitt> ... in particular add something to scroll marker ? property that will choose between navigation mode and I call it "discrete" but we could call it "tabbed" or some other experience<br>
&lt;kbabbitt> ... switch between whether we get tabbed or some other behavior<br>
&lt;kbabbitt> ... as well as role changes and focus order changes<br>
&lt;kbabbitt> ... to obviate the need to use interactivity to remove items from tab order<br>
&lt;kbabbitt> ... not proposing we resolve on exact behavior right now<br>
&lt;kbabbitt> ... just want a resolution for initial keyword on scroll-marker-group to switch between modes<br>
&lt;kbabbitt> ... can have a more detailed proposal at a future meeting<br>
&lt;kbabbitt> ... with goal being we can automatically get correct roles and behaviors in a way less likely for developers to misuse<br>
&lt;Rossen6> q?<br>
&lt;kbabbitt> Rossen6: any feedback?<br>
&lt;fantasai> tabs | links<br>
&lt;fantasai> ?<br>
&lt;schenney> q+<br>
&lt;kbabbitt> flackr: I think fantasai is saying those are possible modes we can use<br>
&lt;TabAtkins> I do like "links" as a much shorter and more direct word to use<br>
&lt;kbabbitt> ... seems reasonable, I chose ? because of aria roles<br>
&lt;kbabbitt> fantasai: you're talking about behavior of whole group<br>
&lt;kbabbitt> flackr: I like it, sounds good<br>
&lt;kbabbitt> ... this is just working name, we'll have to come back and resolve on behaviors<br>
&lt;kbabbitt> Rossen6: PaulG, any opinions from a11y view?<br>
&lt;kbabbitt> PaulG: still need to review<br>
&lt;kbabbitt> Rossen6: no alarms?<br>
&lt;kbabbitt> PaulG: we were asked to come up with, for scroll-marker, ... scroll in general has a lot of issues, differences across OSes<br>
&lt;kbabbitt> ... either UA deals with it or it's your problem<br>
&lt;kbabbitt> ... developers have some good tools<br>
&lt;kbabbitt> ... not sure how we can go further, it's an interactive element of page<br>
&lt;schenney> q-<br>
&lt;kbabbitt> ... until now ? had been kind of omitted, we need to circle up with some folks<br>
&lt;kbabbitt> flackr: more about guidance we should give developers<br>
&lt;kbabbitt> PaulG: not for this discussion, a later thing<br>
&lt;schenney> q+<br>
&lt;kbabbitt> flackr: this is giving devs opportunity to establish correct roles &amp; behavior semantics<br>
&lt;kbabbitt> schenney: in general anything that makes it easier for devs to get a11y right without explicit action is something we should be working towards<br>
&lt;Rossen6> ack schenney<br>
&lt;kbabbitt> ... +1 to having this mode<br>
&lt;kbabbitt> flackr: what I'm proposing is we start to prototype this with specific mode switch as suggested<br>
&lt;kbabbitt> Rossen6: which names are we using?<br>
&lt;kbabbitt> flackr: tabs | links is fine<br>
&lt;kbabbitt> Rossen6: any other feedback or questions or objections?<br>
&lt;kbabbitt> RESOLVED: Add second value to scroll-marker-group as [ tabs | links ]<br>
&lt;kbabbitt> flackr: probably unordered list of properties<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12122#issuecomment-2985032673 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Wednesday, 18 June 2025 16:53:26 UTC