w3c / w3c/csswg-drafts

[css-conditional-5] Queries re font-technology support queries

Open
#7,633 16 comments 1 reaction 1 assignee View on GitHub

@svgeesus is already working on this.

Since Sep 15, 2022.

css-fonts-4 Needs Edits
Dominant language
Bikeshed
Stars
4.9k
Forks
816
PR merge metrics
PR metrics pending

Description

The Conditional Rules level 5 spec 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() appears to accept only keywords, whereas the format() function in the CSS Fonts @font-face src descriptor 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() accepts a single keyword identifying a font technology. In contrast, the tech() function in CSS Fonts 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?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.