- From: Yehonatan Daniv via GitHub <sysbot+gh@w3.org>
- Date: Wed, 14 Jun 2023 08:46:24 +0000
- To: public-css-archive@w3.org
My use-case is a simple page transition, and currently just checking a data attribute which holds the type of visual transition to play. Based on the type I change animation properties on both old and new. Could be also on group if I had other animations. In my use-case it's not temporary, but could definitely change in other scenarios. So I guess it's all of the above. I think it boils down to managing transition state in general. I see 2 options here: 1. It's a "no change", and and agree on the best mechanism for handling state is lifting it up to the `html` element, or maybe even using custom properties on `:root` 2. We define some mechanism for handling that state so that developers are more likely to use it, than to trip on the `:has()` wire And then I guess we communicate it to developers before it gets messy. -- GitHub Notification of comment by ydaniv Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8960#issuecomment-1590753356 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 14 June 2023 08:46:25 UTC