Re: [w3ctag/design-reviews] CSS Overflow Navigation Controls (Carousels) (Issue #1037)

abood640 left a comment (w3ctag/design-reviews#1037)

> こんにちは TAG-さん!
> 
> 
> 
> I'm requesting a TAG review of CSS Overflow Navigation Controls.
> 
> 
> 
> Carousels are an often used design pattern on the web. They are used in a variety of contexts, from product listing pages to slideshow like content. OpenUI has [explored a range of carousel designs](https://open-ui.org/components/carousel.research/), showing that the specific layout and appearance can vary dramatically. They are also provided by many frameworks as components, however implementing a carousel correctly is complicated and often results in inconsistent and sometimes inaccessible implementations.
> 
> 
> 
> There are a [variety of problems being solved by carousels](https://css.oddbird.net/overflow/explainer/), which we believe could be provided by a set of CSS features. Developers could then combine these CSS features to create the various designs. CSS-only component libraries could be built to further simplify this process.
> 
> 
> 
>   - Explainer¹: https://github.com/w3c/csswg-drafts/blob/main/css-overflow-5/carousel-explainer.md
> 
>   - Specification: https://drafts.csswg.org/css-overflow-5/#scroll-navigation, https://drafts.csswg.org/css-multicol-2/#selectordef-column, [interactivity: inert](https://github.com/w3c/csswg-drafts/pull/11178)
> 
>   - WPT Tests: Need to be moved to wpt
> 
>   - User research: https://css.oddbird.net/overflow/explainer/ (Carousel listed among top missing elements https://2023.stateofhtml.com/en-US/usage/#html_missing_elements)
> 
>   - Security and Privacy self-review²: This feature has no known privacy/security concerns. https://drafts.csswg.org/css-overflow-5/#privacy https://drafts.csswg.org/css-overflow-5/#security
> 
>   - GitHub repo: https://github.com/w3c/csswg-drafts/
> 
>   - Primary contacts:
> 
>       - Robert Flack (@flackr), Google, editor
> 
>       - Tab Atkins (@tabatkins), Google, editor
> 
>   - Organization/project driving the specification: Google
> 
>   - Multi-stakeholder support³:
> 
>     - Chromium comments: Positive, implementation is underway
> 
>     - Mozilla comments: https://github.com/mozilla/standards-positions/issues/1161
> 
>     - WebKit comments: https://github.com/WebKit/standards-positions/issues/447
> 
>   - Status/issue trackers for implementations⁴:
> 
>     - Chromium: [::scroll-marker and ::scroll-marker-group](https://chromestatus.com/feature/5160035463462912), [::scroll-button(*)](https://chromestatus.com/feature/5093129273999360), [interactivity: inert](https://chromestatus.com/feature/5107436833472512)
> 
> 
> 
> Further details:
> 
> 
> 
>   - [x] I have reviewed the TAG's [Web Platform Design Principles](https://www.w3.org/TR/design-principles/)
> 
>   - Relevant time constraints or deadlines:
> 
>   - The group where the work on this specification is currently being done: CSSWG
> 
>   - The group where standardization of this work is intended to be done (if different from the current group):
> 
>   - Major unresolved issues with or opposition to this specification:
> 
>   - This work is being funded by:



-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/1037#issuecomment-2984708143
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/1037/2984708143@github.com>