- From: Lea Verou via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Oct 2021 09:35:38 +0000
- To: public-css-archive@w3.org
Please note that the TAG feedback was not "You **must** use `@supports`" but "Please exhaust the possibility of using existing mechanisms for feature support before introducing a new one" ([src](https://github.com/w3ctag/design-reviews/issues/666#issuecomment-901220221)). The TAG does not enforce any particular design, that is not the point of a design review. At this point, the issue has been discussed thoroughly in the CSS WG, and there are some notable practical advantages to an inline syntax. Furthermore, a list of keywords is not a microsyntax, otherwise half of CSS properties would be using microsyntaxes. The worst of all worlds is the current state of specs, with two *different* syntaxes for querying support for font technology, this is one we should move away from as soon as possible. Personally I think what @fantasai suggests is reasonable, assuming it's just a list of keywords and nothing else. -- GitHub Notification of comment by LeaVerou Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6520#issuecomment-935845917 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 6 October 2021 09:35:40 UTC