- From: Dominik Röttsches via GitHub <sysbot+gh@w3.org>
- Date: Wed, 07 Apr 2021 09:55:59 +0000
- To: public-css-archive@w3.org
drott has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-fonts] size-adjust: descriptor and baseline placement / line-height computation == A new test for `size-adjust` [size-adjust-01.html](http://wpt.live/css/css-fonts/size-adjust-01.html) made by @jfkthame expects the baseline of the 150% size-adjust case to shift down due to the Ahem glyphs being scaled up. This ref test expresses as the expectation for `size-adjust` being equivalent to <span> elements for each uppercase letter at 150% font size. ([see ref expectation](https://github.com/web-platform-tests/wpt/blob/master/css/css-fonts/size-adjust-01-ref.html)) This test fails in Chromium's implementation, as for the 150% `size-adjust` case it's scaling the glyphs but not shifting the baseline and not changing the inline line height computation, as much as I can tell. The current spec wording says: > "All metrics associated with this font—including glyph advances, baseline tables, and overrides provided by @font-face descriptors—are scaled by the given percentage, as are the rendered glyph images." My interpretation is that as a consequence, line height and baseline placement should be computed based on scaled / `size-adjust`ed metrics, not based on unscaled metrics and Firefox' behaviour passing this test is correct. Posting this here as an issue just to confirm that that is the intended behaviour. Opinions? Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6189 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 7 April 2021 09:56:01 UTC