Re: [w3ctag/design-reviews] CSS inert (Issue #1055)

argyleink left a comment (w3ctag/design-reviews#1055)

I just mentioned some library and developer feedback on  https://github.com/w3c/csswg-drafts/issues/10711#issuecomment-2762007667 that I feel are meaningful use cases that CSS inert is best suited to support:

- Crawling a tree with JS to be picky about which nodes are inert or not? **CSS does that with selectors**
- Adapting a tree crawl or UI to various screen sizes to manage whether or not items are offscreen inert or on screen and interactive? **CSS does that with media queries**
- Knowledge of whether or not the inert item is actually off screen or just obscured in other UI layering creative design ways? **CSS is already orchestrating those moments** and knows best when to change it

It's very meaningful to use conditional inert strategies to guide users to focusable content. Applications balance this very complex task these days, and developers are reporting that inert is a bit too rigid. CSS can pick up these moments, enhance and guide user experiences.

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

Message ID: <w3ctag/design-reviews/issues/1055/2762905148@github.com>