- From: Jan Nicklas via GitHub <sysbot+gh@w3.org>
- Date: Tue, 06 May 2025 19:35:25 +0000
- To: public-css-archive@w3.org
@benface thank you that helped I still believe this idea could have exactly the opposite effect of what's intended and lead to even worse workarounds. The API won't change the fact that this exact requirement exists on very, very many websites. That's why there are already many (often buggy) workarounds today that use javascript with set `inert` attributes Devs who are asked to implement such a requirement might reach out to a workaround like this: ```css html:where(:has(.no-inert)) *:where(:not(:has(.no-inert))) { interactivity: inert; } .no-inert, .no-inert * { interactivity: auto; } ``` -- GitHub Notification of comment by jantimon Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10711#issuecomment-2855729313 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 6 May 2025 19:35:26 UTC