- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Wed, 26 Sep 2018 19:16:59 +0000
- To: public-css-archive@w3.org
Mainly, I don't understand why there is any issue. The worries seem to be - using ch might cause a font to be downloaded that otherwise would not be - doing a system font fallback for an unused character is a blocking operation ch is defined to use *the actual font* that is used for rendering. The two things noted above would only occur if: - the font actually used has no glyph for "0", AND - the font actually used has no .notdef (in this case, it would be a faulty font, or the font subsetter was faulty) Also, falling back to another font for the width of "0" or .notdef misses the point of using *the actual font*. So my preference would be an ordered list of things to try: 1) the width of the "0" glyph. if it doesn't have one, 2) the width of the .notdef glyph. if it doesn't have one (and thus, the font is broken), 3) use 0.5em No additional webfont is ever downloaded, no additional local font is loaded either. -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3135#issuecomment-424837225 using your GitHub account
Received on Wednesday, 26 September 2018 19:17:01 UTC