- From: Guillaume via GitHub <sysbot+gh@w3.org>
- Date: Sat, 09 Nov 2024 08:06:10 +0000
- To: public-css-archive@w3.org
(My previous comment is confusing as to my understanding of "full support of a property", sorry.) You think authors would use `@supports (property)` to query the "full support of a property", which would be determined as whether the UA parses and interprets (uses) any value defined as valid for that property in the different specifications, which is volatile, agree. You do not think they (or at least not most of them) would use it to query whether the UA "understands" `property`, ie. whether they know it, regardless of any value. But you think it is fine to use `@supports (@rule)` to query the support of an at-rule, determined as whether the UA knows it, regardless of its contents (prelude and block value). As it can be seen in the StackOverflow issue linked in the initial comment, many authors do not even know that `@supports (name: value)` is only for properties. But the number of use cases for `@supports (property)` evaluated as wheter the UA knows `property` is small... so the absence of this feature, which is inconsistent with the presence of the `at-rule(@rule)` feature, is probably fine. -- GitHub Notification of comment by cdoublev Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/11159#issuecomment-2466111280 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Saturday, 9 November 2024 08:06:10 UTC