- From: Chris Lilley via GitHub <noreply@w3.org>
- Date: Tue, 10 Mar 2026 20:37:02 +0000
- To: public-css-archive@w3.org
> I think the spec should be clarified to handle ranges (see below) > such that specifying a range is equivalent to specifying duplicate font-face rules for each value in the range. Close but not quite right. (Font weight descriptors are [not restricted to integer values](https://drafts.csswg.org/css-values-4/#number-value)) However, looking at [CSS Fonts 4, section 5.2, step 4](https://drafts.csswg.org/css-fonts-4/#font-style-matching): (my emphasis) > If a font family match occurs, the user agent assembles the set of font faces in that family and then narrows the set to a single face using other font properties in the order given below. **Fonts might be present in this group which can support a range of [font-width](https://drafts.csswg.org/css-fonts-4/#propdef-font-width), [font-style](https://drafts.csswg.org/css-fonts-4/#propdef-font-style), or [font-weight](https://drafts.csswg.org/css-fonts-4/#propdef-font-weight) properties. In this case, the algorithm proceeds as if each supported combination of values is a unique font in the set. If such a font is ultimately selected by this algorithm, particular values for font-width, font-style, and font-weight must be applied before any layout or rendering occurs.** So I assert that the spec already covers this exact case. The quote in the original post is [from CSS Fonts 3](https://www.w3.org/TR/css-fonts-3/#font-style-matching) (which does not support variable fonts and does not support ranges in descriptors) Closing as invalid. Also, please do not look at CSS Fonts 3, which is [from 2018](https://www.w3.org/TR/css-fonts-3/); what everyone implements is CSS Fonts 4 from, erm, [a week ago](https://www.w3.org/TR/css-fonts-4/). A lot has happened in the last 18 years. And CSS Fonts 4 should really be in CR. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/13626#issuecomment-4034314645 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 10 March 2026 20:37:03 UTC