W3C home > Mailing lists > Public > public-css-archive@w3.org > June 2019

Re: [csswg-drafts] [css-fonts] Clarify how the computed font-size is determined for size keyword (#3906)

From: L. David Baron via GitHub <sysbot+gh@w3.org>
Date: Sun, 02 Jun 2019 20:16:50 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-498061946-1559506609-sysbot+gh@w3.org>
Gecko used to have relatively complicated code to handle the case where a descendant inherited a font size or used a `%`, `em`, etc., font size while being different from its ancestor in terms of `monospace` or not, which would try to redo the font size computation from the nearest absolute ancestor as monospace or not.  I think much of that code is gone (cc @Manishearth) but I don't remember for sure.

I'd also note that a number of years ago I had [a proposal](https://lists.w3.org/Archives/Public/www-style/2010Mar/0206.html) for replacing these separate font size preferences for `monospace` and non-`monospace` with a new value of `font-size-adjust`.

Gecko's defaults appear to be (at a quick skim, hopefully I didn't miss anything):

| script | variable size | monospace size |
| -------- | --------------- | ------------------------ |
| western, cyrillic, ar, el, he, "unicode" (undetected) | 16 | 13 on mac/win, 12 on linux/android |
| ja, ko, zh-CN, zh-HK, zh-TW | 16 | 16 |
| th, devanagari, tamil, armn, beng, cans, ethi, geor, gujr, guru, khmr, mlym, orya, telu, knda, sinh, tibt, math | 16 | 13 |

GitHub Notification of comment by dbaron
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3906#issuecomment-498061946 using your GitHub account
Received on Sunday, 2 June 2019 20:16:51 UTC

This archive was generated by hypermail 2.4.0 : Tuesday, 5 July 2022 06:41:49 UTC