- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Fri, 04 Nov 2022 19:15:56 +0000
- To: public-css-archive@w3.org
We [used to have the concept of a font database](https://www.w3.org/TR/2008/REC-CSS2-20080411/fonts.html#q1), and `@font-face` _adding to_ that database. IIRC this was kind of like a hidden set of `@font-face` with `local` src, describing all the local fonts. The implication of that model would be that the descriptors would have their initial values, so the `unicode-range` would be the initial "all of Unicode" range. I wonder if we could usefully resurrect that concept? Alternatively we could just use a negative: > The first available font, used for example in the definition of [font-relative lengths](https://drafts.csswg.org/css-values-4/#font-relative-length) such as [ex](https://drafts.csswg.org/css-values-4/#ex) or in the definition of the [line-height](https://drafts.csswg.org/css2/#propdef-line-height) property, is defined to be the first font whose glyph for the U+0020 (space) character is not excluded by [unicode-range](https://drafts.csswg.org/css-fonts/#descdef-font-face-unicode-range), given the font families in the [font-family](https://drafts.csswg.org/css-fonts/#propdef-font-family) list (or a user agent’s default font, if none are available). -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4796#issuecomment-1304050014 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 19:16:02 UTC