- From: CSS Meeting Bot via GitHub <noreply@w3.org>
- Date: Wed, 18 Jun 2025 16:53:26 +0000
- To: public-css-archive@w3.org
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> <kbabbitt> flackr: one of the biggest points of feedback we got on scroll marker pseudo<br> <kbabbitt> ... is that these are used for many different use cases<br> <kbabbitt> ... not all of which are tabs<br> <kbabbitt> ... and our use of the tab rules on scroll marker pseudos is not always appropriate<br> <kbabbitt> ... I'm proposing that we have a mode switch property<br> <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> <kbabbitt> ... switch between whether we get tabbed or some other behavior<br> <kbabbitt> ... as well as role changes and focus order changes<br> <kbabbitt> ... to obviate the need to use interactivity to remove items from tab order<br> <kbabbitt> ... not proposing we resolve on exact behavior right now<br> <kbabbitt> ... just want a resolution for initial keyword on scroll-marker-group to switch between modes<br> <kbabbitt> ... can have a more detailed proposal at a future meeting<br> <kbabbitt> ... with goal being we can automatically get correct roles and behaviors in a way less likely for developers to misuse<br> <Rossen6> q?<br> <kbabbitt> Rossen6: any feedback?<br> <fantasai> tabs | links<br> <fantasai> ?<br> <schenney> q+<br> <kbabbitt> flackr: I think fantasai is saying those are possible modes we can use<br> <TabAtkins> I do like "links" as a much shorter and more direct word to use<br> <kbabbitt> ... seems reasonable, I chose ? because of aria roles<br> <kbabbitt> fantasai: you're talking about behavior of whole group<br> <kbabbitt> flackr: I like it, sounds good<br> <kbabbitt> ... this is just working name, we'll have to come back and resolve on behaviors<br> <kbabbitt> Rossen6: PaulG, any opinions from a11y view?<br> <kbabbitt> PaulG: still need to review<br> <kbabbitt> Rossen6: no alarms?<br> <kbabbitt> PaulG: we were asked to come up with, for scroll-marker, ... scroll in general has a lot of issues, differences across OSes<br> <kbabbitt> ... either UA deals with it or it's your problem<br> <kbabbitt> ... developers have some good tools<br> <kbabbitt> ... not sure how we can go further, it's an interactive element of page<br> <schenney> q-<br> <kbabbitt> ... until now ? had been kind of omitted, we need to circle up with some folks<br> <kbabbitt> flackr: more about guidance we should give developers<br> <kbabbitt> PaulG: not for this discussion, a later thing<br> <schenney> q+<br> <kbabbitt> flackr: this is giving devs opportunity to establish correct roles & behavior semantics<br> <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> <Rossen6> ack schenney<br> <kbabbitt> ... +1 to having this mode<br> <kbabbitt> flackr: what I'm proposing is we start to prototype this with specific mode switch as suggested<br> <kbabbitt> Rossen6: which names are we using?<br> <kbabbitt> flackr: tabs | links is fine<br> <kbabbitt> Rossen6: any other feedback or questions or objections?<br> <kbabbitt> RESOLVED: Add second value to scroll-marker-group as [ tabs | links ]<br> <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