- From: Tim Nguyen via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 Mar 2023 09:32:29 +0000
- To: public-css-archive@w3.org
In terms of developer experience and intuitiveness, @kizu's proposal is a lot better than a pseudo-class/element. I think the names could be bikeshed, but this is closer to my mental model of how I see this issue.
> I guess, this could come too close to mixins though — I immediately though of using an infinite transition to always apply that initial state, and how it could interplay with CSS variables etc etc :) So maybe just @initial-state selector {} or @initial-state { selector {} } could be better in that it won't deal with the dynamic custom properties.
I think the pseudo-class/element would have the same issue though, since the whole point is for them to work with transitions.
--
GitHub Notification of comment by nt1m
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8174#issuecomment-1451566130 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 2 March 2023 09:32:31 UTC