- From: Robert Flack via GitHub <noreply@w3.org>
- Date: Thu, 20 Nov 2025 22:08:55 +0000
- To: public-css-archive@w3.org
This is implemented behind experimental web platform features in chromium. I have built a demo to showcase two carousels using each of the two modes at https://flackr.github.io/web-demos/css-overflow/scroll-marker-type/ This is what was proposed in https://github.com/w3c/csswg-drafts/issues/12122#issuecomment-2920507737 using tabs or links instead of discrete or navigation respectively as per resolution in https://github.com/w3c/csswg-drafts/issues/12122#issuecomment-2985032673. Last time we discussed it, the presumption was that we would revisit once we had all of the specifics worked out - I believe they have all worked out as was previously proposed. Shall we take a resolution to adopt these changes? Motivation: In my [demo](https://flackr.github.io/web-demos/css-overflow/scroll-marker-type/) I outline all of the automatic benefits of this mode switch that developers no longer need to do extra work to get right. If you contrast this with all of the considerations that must be made with the feature previously, as [outlined here](https://flackr.github.io/web-demos/css-overflow/a11y-examples/), the complexity is significantly reduced making it much more likely that developers using this feature will have the correct behaviors, appropriate roles, and semantics for these use cases. -- GitHub Notification of comment by flackr Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12122#issuecomment-3560274596 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 20 November 2025 22:08:56 UTC