- From: jfkthame via GitHub <sysbot+gh@w3.org>
- Date: Mon, 22 Aug 2022 19:08:25 +0000
- To: public-css-archive@w3.org
jfkthame has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-conditional-5] Queries re font-technology support queries == The [Conditional Rules level 5 spec](https://drafts.csswg.org/css-conditional-5/#at-supports-ext) extends `@supports` with new `font-tech()` and `font-format()` functions. In looking to implement these, a few minor questions have come up that I'd like to clarify/confirm. (1) The [syntax for `font-format()`](https://drafts.csswg.org/css-conditional-5/#typedef-supports-font-format-fn) appears to accept only keywords, whereas the `format()` function in the CSS Fonts [@font-face src descriptor](https://drafts.csswg.org/css-fonts-4/#font-format-values) accepts either a keyword or a string. While I think keywords are preferable here, I wonder whether we should also accept the string syntax in `@supports font-format(...)` for consistency with the `@font-face` descriptor? (2) The [syntax for `font-tech()`](https://drafts.csswg.org/css-conditional-5/#typedef-supports-font-tech-fn) accepts a single keyword identifying a font technology. In contrast, the [`tech()` function in CSS Fonts](https://drafts.csswg.org/css-fonts-4/#font-face-src-parsing) accepts a comma-separated list of font technology keywords. Should `@supports font-tech(...)` similarly accept a list? (3) A really minor issue, but I have found myself repeatedly writing things like `@supports font-tech(features-opentype)`, and not getting the expected result because the correct keyword is `feature-opentype` (singular). To my mind, the `feature-*` keywords would read more naturally in the plural form (similarly to `font-tech(variations)`). Should we change them to plural, here and in CSS Fonts, before this is widely implemented and webcompat becomes a constraint? Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/7633 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 22 August 2022 19:08:27 UTC