- From: Miriam Suzanne via GitHub <sysbot+gh@w3.org>
- Date: Wed, 15 Feb 2023 17:08:09 +0000
- To: public-css-archive@w3.org
The inline `if()` would have advantages in several cases: - For cases where an author needs different conditions for individual properties, the container at-rule becomes very repetitive. - All the use-cases that could be applied to web components with a host and shadow-dom (where a host is built-in) can also be applied to 'components' built with normal elements and no shadow dom. In those cases, there is no guarantee of a container. There's no reason for us to consider shadow-dom the primary use-case for these features. - As noted by @LeaVerou above, in the context of a property we can allow comparing eg numbers with percentages. > Since if() is used on a specific property, resolving all values is possible, so the constraints of the container query syntax don't really apply. -- GitHub Notification of comment by mirisuzanne Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8446#issuecomment-1431700530 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 15 February 2023 17:08:11 UTC