Post

Luke
@lukewarlow.dev

My site's image carousel is using the new stuff where supported and fallsback to showing a scrollbar where it's not. Does the job for what I need.

Niklas
@nilaallj.se

I’m curious about why there are `scroll-state(snapped)` container queries, while the specification (Scroll Snap level 2 to be specific) contains `:snapped` pseudo classes. Are they for different use cases?

Adam Argyle
@nerdy.dev

it's just a scroller if there's no support these carousel features are just "added affordances" to help users discover and navigate

Adam Argyle
@nerdy.dev

been behind flags for months, the specs have been thoroughly evaluated, we've been tons of proofs, and yep, v1 of it all is ready we're not done yet!

Adam Argyle
@nerdy.dev

of course! they havent stated when they're start working on it, but they helped create the specs and reviewed all the work along the way. it's been many years in the making 😁

Rasmus Fløe
@phloe.co

Stoked to see these primitives. A boon for accessibility and consistency! People love swiping these sort of things on touch devices... should we have a native way of enabling swiping for mouse users? 🤔 (It's a pain to implement in userland 😅)

Adam Argyle
@nerdy.dev

browser takes care of: ✅ the stateful buttons and their accessibility ✅ the stateful markers (dots/thumbnails/etc) and their accessibility the buttons :disable at the edge, the dots are :target-current when their related item is snapped or in view, keyboard interactions are all setup, and more!!