- From: fantasai via GitHub <sysbot+gh@w3.org>
- Date: Wed, 27 May 2020 20:26:19 +0000
- To: public-css-archive@w3.org
Based on the discussion, seems like we should continue to say that the computed font-size is unaffected, and take @emilio’s suggestion of maintaining a multiplier, which will affect the used font size and other effects that key off of the used font size (which is a class of things we'll henceforth need to be more clear about). I think the only things that need to key off the used font size are going to be anything (other than actual `<length>` values) that keys off the font-size or a character size in the css-text, css-text-decor, and css-inline modules. Scanning through, looks like that list should include: - `baseline-shift` percentage values if `line-height` is also a percentage (thus referencing the `font-size` but not via `em` units) - `letter-spacing` and `word-spacing` percentage values - `tab-size` number values - `text-decoration-*` percentage values - `text-underline-offset` percentage values Some side effects: - Need to decouple `line-height` percentages from em units, as they'll behave differently here. (And should have been different from the start but that ship sailed a couple decades ago.) - If we need another concept of "used font size", e.g. if we introduce per-font multipliers against `font-size` to optically equalize glyphs across a fallback list, then we need to be careful not to conflate terminology with what we're doing here. That kind of effect should not be accounted for here. -- GitHub Notification of comment by fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4988#issuecomment-634920474 using your GitHub account
Received on Wednesday, 27 May 2020 20:26:20 UTC