- From: Yehonatan Daniv via GitHub <noreply@w3.org>
- Date: Tue, 24 Mar 2026 16:25:52 +0000
- To: public-css-archive@w3.org
Thanks for opening this! It's a tough call for sure. I do like the way this allows authors to define explicitly how/where the state is handled. And this is also a very straightforward solution for problem of managing state of multiple triggers. On the other hand, the counter example above is somewhat unfortunate, and there are others. But, in this case this is fixed with simply adding a single property. We should also resolve how stateless triggers work here. I assume they simply act regardless of state, and don't affect it in any way, regardless of the action they are set to. -- GitHub Notification of comment by ydaniv Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13710#issuecomment-4119644679 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 24 March 2026 16:25:52 UTC