- From: Nigel Megitt via GitHub <sysbot+gh@w3.org>
- Date: Fri, 04 Nov 2022 15:31:10 +0000
- To: public-css-archive@w3.org
Just been drawn to this via https://github.com/w3c/ttml2/pull/1242#discussion_r683631831 and I have a question. Given the updated text defines "[first available font](https://www.w3.org/TR/css-fonts-4/#first-available-font)" in terms of the [unicode-range](https://www.w3.org/TR/css-fonts-4/#descdef-font-face-unicode-range) property, which itself is a descriptor that is defined for [`@font-face`](https://www.w3.org/TR/css-fonts-4/#descdef-font-face-unicode-range), what is the intent relating to fonts that are available, installed, and referenced by `font-family` _without_ an `@font-face` rule? Since such fonts do not have an applicable `unicode-range` property, they can never be the "first available font", even if they do support the 0x0020 code point. Is there an assumption that the character map for each font in the `font-family` list will be queried (of course, after applying any `@font-face` rules)? If so, it seems like we should use some other term than `unicode-range`. For example could we change: > the first font whose [unicode-range](https://www.w3.org/TR/css-fonts-4/#descdef-font-face-unicode-range) includes the U+0020 (space) character to > the first font whose [character map](https://www.w3.org/TR/css-fonts-4/#descdef-character-map) includes the U+0020 (space) character ? -- GitHub Notification of comment by nigelmegitt Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4796#issuecomment-1303767427 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 4 November 2022 15:31:11 UTC