- From: Chris Lilley via GitHub <sysbot+gh@w3.org>
- Date: Fri, 21 Feb 2020 19:24:49 +0000
- To: public-css-archive@w3.org
Related: https://github.com/w3c/csswg-drafts/issues/1800 https://github.com/w3c/csswg-drafts/issues/1804 and > [WebKit doesn’t do this; it just uses the primary font, and if the primary font doesn’t support “0” then it uses that font’s .notdef glyph. No downloads necessary](https://github.com/w3c/csswg-drafts/issues/3135#issue-362776570). and > [So my preference would be an ordered list of things to try: * the width of the "0" glyph. if it doesn't have one, * the width of the .notdef glyph. if it doesn't have one (and thus, the font is broken), * use 0.5em](https://github.com/w3c/csswg-drafts/issues/3135#issuecomment-424837225) -- GitHub Notification of comment by svgeesus Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4796#issuecomment-589798428 using your GitHub account
Received on Friday, 21 February 2020 19:24:51 UTC