W3C home > Mailing lists > Public > public-css-archive@w3.org > September 2017

Re: [csswg-drafts] [css21][css-inline] Meta bug for line height

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 13 Sep 2017 16:21:47 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-329220943-1505319697-sysbot+gh@w3.org>
The Working Group just discussed `Meta bug for line height`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Meta bug for line height<br>
&lt;astearns> https://github.com/w3c/csswg-drafts/issues/1796#issuecomment-328713658<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/1796#issuecomment-328713658<br>
&lt;dael> astearns: I wanted to introduce this work because I think it needs more review. I'd like dbaron and others to look at this nest so we can have useful discussion and start resolving things to make line height more interop<br>
&lt;dael> florian: I think the result of my testing is we're more interop then I thought. Spec is wrong. I think there's 2 places we're not. One is how browsers fetch font metrics, there are differences and I didn't try and understand them.<br>
&lt;Chris> q+<br>
&lt;astearns> ack Chris<br>
&lt;dael> florian: One other exception is what happens with the first available font when the space character is excluded from unicode. WE did resolve there recently, but I think we went a bit too fast. I made test cases for every assertion, so please go review. If you agree with me I'll make PR for the spec. If you don't I'll look<br>
&lt;dael> Chris: There's a commonly used trick where you use unicode and rely on a second font after the swishy first font.<br>
&lt;dael> florian: I think your trick only works in chrome<br>
&lt;dael> Chris: Generally in FF too.<br>
&lt;dael> florian: Please look at my test cases and tell me where it's wrong. In FF it goes with random stuff and speed of load changes what you get. I have a test case.<br>
&lt;dael> Chris: Okay, I'll go review.<br>
&lt;dael> florian: Please everyone go reivew and based on that we can have a spec that matches impl and impl that match each other.<br>
&lt;Chris> s/unicode/unicode to get a swash ampersand/<br>
&lt;dael> astearns: Anyone else have something on this topic?<br>
&lt;dael> astearns: Thanks florian for doing this.<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1796#issuecomment-329220943 using your GitHub account
Received on Wednesday, 13 September 2017 16:21:50 UTC

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