- From: Dominik Röttsches via GitHub <sysbot+gh@w3.org>
- Date: Wed, 06 Oct 2021 09:09:34 +0000
- To: public-css-archive@w3.org
Thanks for summarizing your remaining feedback. > * Extend the `format()` function to take keywords after the format string. These keywords represent the various font tech features. This allows simple forking of the URL, and can ship first. That's the thing I tried to ship and received the feedback from TAG that micro-syntax is to be avoided there. Even if we flatten the grammar here to a sequence of keywords, it's still a simple grammar. The TAG's recommendation [was to consider using `@supports`](https://github.com/w3ctag/design-reviews/issues/666#issuecomment-901220221), which we resolved on. > * Extend `@supports` to add a `font-format()` function with identical syntax. This allows higher-level conditionals that can control more than just the download URL. It was my understanding (@svgeesus and @LeaVerou 's as well, as stated in #6635) that we remove the `format()` syntax in the src: descriptor. It seems to me that that also better follows the intention of the TAG's advice on avoiding micro-syntax. Even if we reference the syntax for format() in `src:` from CSS conditionals grammar, the way I interpret the TAG's feedback is not not have complex syntax in a very particular place outside `@supports`. > * Add `@else` to allow fallback rules to be easily made conditional on negation of the `@supports` query. `@when` and `@else` were already added, per #112, https://drafts.csswg.org/css-conditional-4/#else-rule in daeb7c32425c69e63355dd2580deff41ccc4ec4c and 0a8f9f90f0095c17328dfccd9eacda77d66ba693, weren't they? So now that we have the `font-technology()` function in for `@supports`, and we have `@when` in the spec, it looks to me like we're in a good spot. I also don't see any alternative font container or compression formats that strictly restrict or bring their own font features other than SFNT / OpenType and WOFF2. In other words, everything's in an OpenType container these days, optionally WOFF(2) compressed, whether it's OpenType layout, AAT, graphite, color or non color, variable or not. But we do have the flexibility of adding format keywords in the `font-technology()` function as needed for alternatives if they arise. -- GitHub Notification of comment by drott Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6520#issuecomment-935804411 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:09:36 UTC