← Back to release summary

Auto range support for font descriptors inside @font-face rule

Category

CSS

Type

Chromium catches up

Status

Enabled by default (Chrome 109)

Intent stage

Start prototyping

• Breaking change: No
• Enterprise impact: None
• Spec maturity: Published standard
• Web Platform Tests: No

WPT details: Tests for 'font-stretch' descriptor: https://wpt.fyi/results/css/css-fonts/font-face-stretch-auto-static.html https://wpt.fyi/results/css/css-fonts/font-face-stretch-auto-variable.html https://wpt.fyi/results/css/css-fonts/font-face-stretch-default-variable.html Tests for 'font-style' descriptor: https://wpt.fyi/results/css/css-fonts/font-face-style-auto-static.html https://wpt.fyi/results/css/css-fonts/font-face-style-auto-variable.html https://wpt.fyi/results/css/css-fonts/font-face-style-default-variable.html Tests for 'font-weight' descriptor: https://wpt.fyi/results/css/css-fonts/font-face-weight-auto-static.html https://wpt.fyi/results/css/css-fonts/font-face-weight-auto-variable.html https://wpt.fyi/results/css/css-fonts/font-face-weight-default-variable.html 'auto' keyword parsing test: *auto* in https://wpt.fyi/results/css/css-fonts/variations/at-font-face-descriptors.html

Summary

Auto range support for variable fonts in 'font-weight', 'font-style' and 'font-stretch' descriptors inside '@font-face' rule.

Motivation

Variable fonts provide users the opportunity to choose how heavy or slanted or wide the typeface should be, rather than having those decided by the type designer. For variable fonts, in Chrome, it is required to add the supported range for 'font-weight', 'font-style' and 'font-stretch' descriptors inside @font-face rule, otherwise variable fonts would either be synthesizing bold faces or the text will appear as normal. In CSS WG issue #2485 it was resolved to add a default keyword 'auto'.

Standards & signals

• Specification: https://drafts.csswg.org/css-fonts/#font-prop-desc
• Firefox: Shipped/Shipping — Variable fonts work without specifying the supported range, however the browser does not yet support auto value parsing. Tests for 'font-stretch' and 'font-weight' descriptors are passing. Although the 'font-style' descriptor has a bug when it is synthetically obliqueing out of the supported range.
• Safari: Shipped/Shipping — Variable fonts work without specifying the supported range, however the browser does not yet support auto value parsing. Tests for 'font-stretch' descriptors are passing. Although the 'font-weight' descriptor works without specifying the range, there are some pixel differences in the test results. 'font-style' descriptor looks like it is synthesizing oblique faces.
• Web developers: Positive — UX engineer, Connie Ye (connieye@google.com) faced this issue when she wasn’t able to use font-weight property without specifying the supported range for the variable font. That’s what she said: “It would be useful if the variable fonts behavior was always consistent with normal fonts, where you don't need to declare font-weight within @font-face”
• Tracking bug: https://bugs.chromium.org/p/chromium/issues/detail?id=973194

Ecosystem

• Web Platform Tests: https://wpt.fyi/results/?q=css%2Fcss-fonts%2Ffont-face-stretch-auto-static
• Chrome Platform Showcase: https://chrome-platform-showcase.paulkinlan-ea.deno.net/features
• GenDN reference: https://gendn.paulkinlan-ea.deno.net/features
• chrome.dev demos search: https://www.google.com/search?q=site%3Achrome.dev+Auto%20range%20support%20for%20font%20descriptors%20inside%20%40font-face%20rule
• MDN Web Docs: https://developer.mozilla.org/en-US/search?q=Auto%20range%20support%20for%20font%20descriptors%20inside%20%40font-face%20rule
• Baseline status: https://webstatus.dev/?q=Auto%20range%20support%20for%20font%20descriptors%20inside%20%40font-face%20rule

Explainers: https://bugs.chromium.org/p/chromium/issues/detail?id=973194 https://drafts.csswg.org/css-fonts/#font-prop-desc

View on chromestatus.com