- From: Dominik Röttsches via GitHub <sysbot+gh@w3.org>
- Date: Fri, 20 Aug 2021 13:23:38 +0000
- To: public-css-archive@w3.org
CC @jfkthame
I'll investigate what that would entail from an implementation point of view (complexity, overhead) and comment once I have some findings.
One consideration from a readability point of view: If we introduce such a @supports clause, we will have both mechanisms: a list of entries in the `src:` descriptor (for example multiple `url()` entries potentially then "legacy" `format("...")` specifiers (with its own semantics of choosing the first compatible one from this list) _and_ potentially multiple `src:` descriptors conditional on `@supports` blocks in the same `@font-face` rule, which I personally do not find great for consistency or readability. In other words, we would change the primary paradigm for `src:` selection to the @supports syntax but would still need to keep compatibility with the current approach of traversing list of entries.
> * It skips the [parsing weirdness for `src`](https://github.com/w3c/csswg-drafts/issues/2920) that this microsyntax has introduced
FWIW, the "parsing weirdness" may be considered addressed or improved with the [most recent change](https://github.com/w3c/csswg-drafts/commit/60dd3ff915b560713b47f4d9b1d0aade6cbb1944) which references the CSS syntax spec for [parsing a comma separated list of components](https://www.w3.org/TR/css-syntax-3/#parse-comma-separated-list-of-component-values).
--
GitHub Notification of comment by drott
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6520#issuecomment-902690451 using your GitHub account
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 20 August 2021 13:23:39 UTC