- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Fri, 28 Jun 2024 19:36:20 +0000
- To: public-css-archive@w3.org
Re-targeted this against css-conditional, since container queries are being moved over there, and out of the contain spec. If we can do something like this, it would be useful. I'd be curious about trying to integrate it more into container queries - but I'm not sure if that only makes it more complicated. The primary limitation here that CQs solve is the potential for dependency loops. As I understand it, that's easier to resolve property by property. If we create a loop with this syntax, does it invalidate the entire block? ```css .foo { --color: pink; background-color: blue; @element style(--color: pink) { --color: not-pink; /* certainly this is invalid */ background-color: pink; /* but is this applied? */ } } ``` I imagine we can come up with an answer to that question, as far as feature design goes. But I'm not sure how hard it is to implement. -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10509#issuecomment-2197516780 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 28 June 2024 19:36:21 UTC