Re: [csswg-drafts] [css-ui] select:hover and select:active styles (#11185)

There are kind of two different conversations happening here. One is about the best name(s) to choose for this feature, to make it clear what's happening. While that's an important question, the other one is about the actual behavior. Maybe we can decide the behavior question first, and then find the best name for it?

The questions I see:
 1. Should this new thing affect Javascript event propagation?  My view (and it sound like the majority view?) is that this new thing should only affect selector matching and *not* event propagation, which is a different thing from how the selectors are defined, and just "happens" to also use the flat tree.
 2. How does this new feature affect things like `querySelector()`, `matches()`, and `:has()`? I think those seem clear - this new feature affects selector matching, and it should therefore "just work" in the same way via e.g. `.matches(':hover')` as it does in a stylesheet with `:hover {}`. 
 3. What CSS properties are "in play" for this new feature? This should be contained to just those properties that are defined with "an element also matches :pseudoclass if one of its descendants in the flat tree matches". That sounds like only these three? [`:hover`](https://drafts.csswg.org/selectors/#hover-pseudo), [`:active`](https://drafts.csswg.org/selectors/#active-pseudo), [`:focus-within`](https://drafts.csswg.org/selectors/#focus-within-pseudo). Are there others?
 4. Should the "containment" of these properties happen via a new CSS property or value, or should it happen at the top layer boundary? I'm personally happy with either solution (those are options 2 and 1, respectively, from [this comment](https://github.com/w3c/csswg-drafts/issues/11185#issuecomment-2551909017)).


> Don't we have precedents for this via modal dialogs / fullscreen? Having a modal dialog open or a fullscreen element turns the rest of the page inert. We might want the same to happen for a `<select>` popup? That'd contain focus and pointer events as well, right?

I think this would be a big mistake. Popovers are not modal, and therefore don't inert the page. For good reason - they're not intended to behave modally. I.e. while you have a `<select>` picker open, you can happily go hover some other element to get a tooltip to show up. Or click on a button elsewhere on the page, which light-dismisses the picker. 

-- 
GitHub Notification of comment by mfreed7
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11185#issuecomment-2583300155 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 10 January 2025 17:18:14 UTC