- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 28 Apr 2021 16:17:35 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[css-fonts] The web de-facto requires nonnegative line gap metrics in fonts`, and agreed to the following: * `RESOLVED: Fonts with negative line gaps are clamp at 0` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: [css-fonts] The web de-facto requires nonnegative line gap metrics in fonts<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/5064<br> <dael> myles: Pretty straightforward. Browsers do it but not in spec.<br> <dael> myles: If font says it has negative line-gap it's clampped at 0<br> <dael> Rossen_: Anyone with different opinion why this shouldn't be the case?<br> <dael> Rossen_: Obj to Fonts with negative line gaps are clamp at 0<br> <dael> florian: Quesiton, have you checked this is true of print formatter?<br> <dael> myles: No, haven't checked. FF, Chrome, and WK do it<br> <dael> florian: Sounds like a good idea, wondering if done in print and how we deal with compat. Maybe just suggest they do it as well<br> <dael> Rossen_: This is why we have standards<br> <dael> RESOLVED: Fonts with negative line gaps are clamp at 0<br> <dael> myles: I think metric is within inline spec so I think this issue should be parented under that spec<br> <dael> Rossen_: Sure<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5064#issuecomment-828587714 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 28 April 2021 16:17:37 UTC