- From: Tim Nguyen via GitHub <sysbot+gh@w3.org>
- Date: Fri, 10 Jan 2025 16:18:23 +0000
- To: public-css-archive@w3.org
> I think you'd struggle to make pointer-events about something more than pointers in a backwards compatible way. Also, if you do that, the feature becomes a real mess. For staters, the naming really sucks - the word 'pointer' is right there. That's not my suggestion fwiw. I was just saying we should approach the problem differently and think about existing primitives (top layer, inert, pointer-events, etc.). If a new primitive is added, I'd at least expect it to fit in the current patterns (e.g. contain/none/auto type values, rather than mentioning specific CSS selectors). > But that I think is an issue that should be fixed for all top layer elements IMO? If we don't somehow make it the default (why not? are there use cases for this?) I wouldn't be opposed to this personally. Top layer sort of conceptually breaks the propagation by laying out everything as a sibling of the root. -- GitHub Notification of comment by nt1m Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11185#issuecomment-2583138049 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 16:18:24 UTC