- From: Amelia Bellamy-Royds via GitHub <sysbot+gh@w3.org>
- Date: Tue, 25 Sep 2018 02:39:21 +0000
- To: public-css-archive@w3.org
I'd strongly say that calculating a `ch` unit (or `ic`, etc.) _shouldn't_ cause a font to download, but I'm not sure that should mean giving up the use of the 0 as the reference glyph. Consider the case of a custom font with just a few special characters (e.g., fancy ampersand) as the first font in the list, with a regular web font or system font as the next font in the stack. Using an artificially calculated value from the first font seems a poor choice if there is a font available (already downloaded or on the system) with a 0. In most CSS environments, there will be at least a default font with a 0 in it. And if there really isn't, the spec already defines a fallback (0.5em). -- GitHub Notification of comment by AmeliaBR Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3135#issuecomment-424188472 using your GitHub account
Received on Tuesday, 25 September 2018 02:39:23 UTC