- From: Joey Arhar via GitHub <noreply@w3.org>
- Date: Wed, 08 Jul 2026 16:02:41 +0000
- To: public-css-archive@w3.org
> That non-custom select doesn't behave like that at all. It seems to keep :hover while open and hovering the picker, at least in Chrome and Firefox. In Chrome it seems to keep it even when the mouse is elsewhere. I don't have a preference on whether the appearance:auto behavior is changed or not, but actually determining whether the pointer is inside the native picker sounds hard, so hopefully we can avoid that with whatever we do for appearance:auto. > That we could've maybe achieved a reasonable result with select:not(:open):hover in the UA stylesheet? Ok, it's not exactly the same, but... given the action of clicking on the select is the same as the action of clicking anywhere else on the page, it seems ok? I don't think it would hurt to add `:not(:open)` to the hover and active styles, but if authors put their own hover or active styles on the select then they would have to also add `:not(:open)`, which they probably wouldn't just know they need to do - the current magic helps authors out. > but it seems we maybe overcomplicated the model a bit for nothing? I think that the benefits of the complicated model are: 1. Authors don't have to add `:not(:open)` and are less likely to accidentally create broken experiences. 2. Other cases of nesting top layer elements inside invokers are also fixed, which also might not have an `:open` selector to use when styling. I admit that there aren't other good examples of where this happens yet for other builtin elements, but authors could already be nesting popovers inside invokers. The implementation complexity doesn't look like that much tome: https://chromium.googlesource.com/chromium/src/+/9a341b91cb6d194a326fb947554171d7befd36d9 -- GitHub Notification of comment by josepharhar Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/14143#issuecomment-4916743511 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 8 July 2026 16:02:42 UTC