- From: Jake Archibald via GitHub <sysbot+gh@w3.org>
- Date: Fri, 10 Jan 2025 09:19:20 +0000
- To: public-css-archive@w3.org
> E.g. you might want `:focus-within` to keep behaving the same for `querySelector()` for the purposes of DOM queries, but prevent the propagation when using it for styling. That's what I was intending with my proposal. It only impacts CSS, not JS. I guess the naming I went with didn't make that clear. I'm sure there's better names out there. > Hence my preference for re-using primitives like `pointer-events` The problem is `:active` and `:focus-within` are not limited to pointers, they can happen through keyboard interaction. `pointer-events` is about hit testing, whereas we're talking about propagation of particular pseudo states that aren't limited to pointers. I'm not tied to my proposal either, but my aim was to provide a property that lets you create a CSS propagation boundary for particular pseudo classes. I don't think it should impact JS events. Would your proposal impact JS events? I worry that would recreate the issue we see with iframes when it comes to things like drag & drop. -- GitHub Notification of comment by jakearchibald Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11185#issuecomment-2582147870 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 09:19:21 UTC