- From: Tim Nguyen via GitHub <sysbot+gh@w3.org>
- Date: Wed, 18 Dec 2024 23:15:13 +0000
- To: public-css-archive@w3.org
> For completeness, is there another option to do nothing yet and rely on a more complex :has selector to accomplish the behavior we want in the UA style rules (with the con of forcing authors to use the more complex selector if they want to override things)?
Authors will likely want to do this too without some complex `:has()`/`:not()` logic.
> select::picker(select) {
> hover-propagation: stop;
> }
> seems relatively easy to understand, doesn't it? It goes right on the "border" element where bubbling should stop. That's in contrast to the proposed variations for #4 where you have to apply a property to an entire sub-tree, minus a "donut" of that sub-tree.
I think it raises more questions than answers. A big one is: does it affect JS mouse events? It's not necessarily obvious from the name.
If we were to go this route, maybe something like `pointer-events: contain` makes more sense? It would end up affecting everything that relates to hit-testing including JS events.
--
GitHub Notification of comment by nt1m
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11185#issuecomment-2552445121 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 18 December 2024 23:15:14 UTC