- From: Sam Atkins via GitHub <sysbot+gh@w3.org>
- Date: Thu, 26 Sep 2024 14:01:44 +0000
- To: public-css-archive@w3.org
AtkinsSJ has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-fonts] Inconsistency with `font-named-instance` descriptor == The definition of [`font-named-instance`](https://drafts.csswg.org/css-fonts/#descdef-font-face-font-named-instance) says it can either be a `<string>` or `auto`, and handles `auto` in this way: > If the [font-named-instance](https://drafts.csswg.org/css-fonts/#descdef-font-face-font-named-instance) descriptor is set to a value other than auto, then the appropriate stage in the [§ 7 Font Feature and Variation Resolution](https://drafts.csswg.org/css-fonts/#font-feature-variation-resolution) will inspect the font file to find the first named instance in the font which has a localized name equal to the given [<string>](https://drafts.csswg.org/css-values-4/#string-value) according to the rules given in [§ 5.1 Localized name matching](https://drafts.csswg.org/css-fonts/#localized-name-matching). However, step 5 of [font-resolution](https://drafts.csswg.org/css-fonts/#font-feature-variation-resolution) describes it as having a `none` value: > If the font is defined via an [@font-face](https://drafts.csswg.org/css-fonts/#at-font-face-rule) rule, that `@font-face` rule includes at least one valid font-named-instance descriptor with a value other than none, and the loaded font resource includes a named instance with that name according to the [§ 5.1 Localized name matching](https://drafts.csswg.org/css-fonts/#localized-name-matching) rules, then all the variation values represented by that named instance are applied. These values are clamped to the values that are supported by the font. It seems to me that font-matching should be looking for a non-`auto` value instead. Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/10952 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 26 September 2024 14:01:45 UTC