Devrel Inquiry: CSS carousel features in 2025

[argyleink]

Is this a bug report, a feature request, or a question?

It's a question.

I devrel for Chrome on CSS and UI stuff, and we've been working hard on standardized carousel features for the web (CSS Overflow 5 Draft Spec). Should be "easy" and accessible to make these things! We have great prototypes in Canary (behind the web experiments flag); I'm curious if y'all are interested in seeing this work, trying the APIs or just chatting round-and-round about carousels?

If no?
close this issue

If yes?
I run WebDev Office Hours all year, would love to get 30m to chat about any or all of these:

• what's difficult for you to manage in this library
  • outstanding bugs you'd like looked at / fixed by Chrome
• the new CSS carousel features
  • scroll buttons: browser generated for an area with overflow
  • scroll markers: browser generated for any of the items in the carousel
  • CSS inert for off screen carousel items
  • and of course these features pair well with
    • scroll driven animation: go off the main thread
    • scroll-state() queries: trigger when overflow, stuck or snapped
    • container queries
    • scroll snap events: new events for snap scrolling
• potential ways these features can integrate with your library

Book a slot with me:
let me know if you need an alternative time and don't feel like you need to prepare anything.

Hope this finds y'all well, I'm here to help 🤘🏻