- From: Dominik Röttsches via GitHub <sysbot+gh@w3.org>
- Date: Fri, 05 Mar 2021 10:05:40 +0000
- To: public-css-archive@w3.org
> One subtle issue is that, what exactly is the value being overridden? It should not be the font-size property value, neither computed nor used, since they work at different levels and should better not have extra dependency. My understanding is the intention is not to use a fully down- or upscaled font internally as that would affect the line height. As @jfkthame explains, ascent / descent would still be computed from `font-size:`, which I think makes sense (otherwise what's the difference to using a different `font-size:` to start with? So perhaps it can be described from an implementation perspective as splitting the internal font object used for retrieving metrics for line height (ascent, descent) in layout from the one that we use to actually perform inline layout with, that we shape with, and that we shape with. Or perhaps more simply put: Keep line height, ascent, descent, baseline computations based on font-size: and original metrics at `font-size:` (taking `ascent-override` etc. into account), but then inside the line, using a scaled font which will operate at the decreased/increased font-size for how it behaves in shaping (scaled advances, shorter/longer text run results) and how it draws (smaller, larger glyphs). -- GitHub Notification of comment by drott Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6075#issuecomment-791315929 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 5 March 2021 10:05:42 UTC