- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Fri, 16 May 2025 13:31:43 +0000
- To: public-css-archive@w3.org
svgeesus has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-fonts-4] Localized font name matching, and WPT == I notice that some WPT, such as [font-family-name-015.xht](https://github.com/web-platform-tests/wpt/blob/6869c15e7e/css/css-fonts/font-family-name-015.xht) have assertions like > The 'font-family' property set to and installed font renders the appropriate font. Localized fullname should not match. This assertion (in what was originally a CSS 2.1 test) contradicts CSS Fonts 4, [5.1. Localized name matching](https://drafts.csswg.org/css-fonts-4/#localized-name-matching) which states: > Some font file formats allow font faces to carry multiple localizations of a particular string (e.g. family name or named instance). User agents must recognize and correctly match all of these names independent of the underlying platform localization, system API used, or document encoding. Presumably this explains some of why no current browser [passes a bunch of these tests](https://wpt.fyi/results/css/css-fonts?label=master&label=experimental&aligned&q=font-family-name) Presumably those tests should be corrected, flipping the pass criteria? @drott @jfkthame Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/12207 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 16 May 2025 13:31:44 UTC