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

Re: [csswg-drafts] [css-rhythm-1] Avoiding accidental double spacing

From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
Date: Wed, 03 May 2017 16:47:23 +0000
To: public-css-archive@w3.org
Message-ID: <issue_comment.created-298968697-1493830042-sysbot+gh@w3.org>
The CSS Working Group just discussed `Avoiding accidental double spacing`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: Avoiding accidental double spacing<br>
&lt;dael> Github topic: https://github.com/w3c/csswg-drafts/issues/938<br>
&lt;dael> Florian_:  I think we shouldn't rehase that issue in github.  I think we need to sort out another issue first. We had been talking about what line-height normal means at F2F and discovered we don't even know what line-height: number means.<br>
&lt;dael> koji: There are details to get out. As long...in terms of line-height consistancy, I think dbaron confirmed it's consistant.<br>
&lt;dael> Florian_: I don't think we concluded. WE said prob is, but we have 3 behaviors on the white board. We weren't sure.<br>
&lt;dael> koji: All on consistant for line-height<br>
&lt;dael> Florian_: No they're not.<br>
&lt;dael> koji: They were.<br>
&lt;dael> Florian_: 2 are, one isn't.<br>
&lt;dael> Florian_: The black behavior does not result in the same line-height as blue a nd red.<br>
&lt;dael> Florian_: We weren't sure which Edge did. We didn't have full answers.<br>
&lt;dbaron> Only one of the three is consistent for line-height if you have font fallback<br>
&lt;dael> Florian_: My prop on double s paces depending on line-height.<br>
&lt;fantasai> diagram: https://lists.w3.org/Archives/Public/www-archive/2017Apr/att-0008/IMG_20170421_173959.jpg<br>
&lt;dael> koji: I think I have tests on this already.<br>
&lt;dael> Florian_: If you have tests, when were they shared?<br>
&lt;dael> koji: In this issue.<br>
&lt;dael> koji: As far as I tested it's interop.<br>
&lt;Florian_> https://github.com/w3c/csswg-drafts/issues/1254<br>
&lt;dael> Florian_: When we discussed at F2F no one knew for sure. If you do know ^ is where we discussed that.<br>
&lt;dael> astearns: koji can you post a link to your test cases?<br>
&lt;koji> http://output.jsbin.com/xekuhu<br>
&lt;astearns> http://output.jsbin.com/xekuhu<br>
&lt;dael> astearns: Is it ^?<br>
&lt;dael> astearns: There we go.<br>
&lt;dael> Florian_: Okay.<br>
&lt;dael> astearns: koji can you desc what it's checking?<br>
&lt;dael> koji: This is a test case we discussed. 5 in the graph and line-height nromal. You can see the line-height is same. If you hae 5 line-height it's maybe different. 0,4 have 1.2, 1.5, 1.8<br>
&lt;dael> koji: You can see it's consistant height.<br>
&lt;dbaron> Does this testcase have font metrics that would trigger the issues we discussed?<br>
&lt;dael> Florian_: I can't figure out which browser is what color.<br>
&lt;dael> fantasai: You need a case with fallback in the line. Where you have difference scripts all on the sameline. Have that trigger different fonts with different ascent &amp; decent metrics.<br>
&lt;dael> MaRakow: You need a font with crazy high and crazy low ascent/descent.<br>
&lt;MaRakow> s/MaRakow/???/<br>
&lt;myles_> s/MaRakow/myles_/<br>
&lt;dael> Florian_: I think this is a bit too tricky on the fly. Until we call agree what line-height: number and line-height: normal means it'll be hard to solve.<br>
&lt;dael> Florian_: If we agree enough that size is the same that could be enough to discuss. Doc about behavior isn't there.<br>
&lt;dael> koji: I thought [missed]<br>
&lt;dael> astearns: I think I heard you say browsers agree on line-height, but not glyph in line-box. Correct?<br>
&lt;dael> koji: Yeah. one this we agreed is to match existing impl. If they all agree on line-height: n umber I don't see problems.<br>
&lt;dael> Florian_: I don't think we established they agree.<br>
&lt;liam> s/not glyph in/not glyph-position in/<br>
&lt;dael> fantasai: We said  impl will agree if they confirm to CSS2 because we agreed to change CSS2 to say that the black behavior is not allowed. So if immpl follows spec line0height will be that number. If impl don't follow they have to change.<br>
&lt;dael> dbaron: I don't htink that's what we agreed.<br>
&lt;dael> Florian_: I think that was a preliminary conclusion.<br>
&lt;dael> dbaron: I think what we agreed only produces it if there's a single element. It doesn't work with multiple when some have font-fallback.<br>
&lt;dael> astearns: Did I hear myles_ volunteer to make test fonts?<br>
&lt;dael> myles_: I can do that easily.<br>
&lt;dbaron> s/with multiple/if there are multiple elements on the line/<br>
&lt;dael> astearns: Thank you.<br>
&lt;Rossen_> https://lists.w3.org/Archives/Public/www-archive/2017May/0000.html<br>
&lt;myles_> please ACTION me<br>
&lt;myles_> bkardell_: there are many fonts named that 😇<br>
&lt;myles_> (test fonts)<br>
&lt;dael> astearns: I think we need to get past this Q about what CSS 2 will say about line height and if impl will be able to match. Then figure out cases where that's not enough for consistant line height.<br>
&lt;dael> astearns: Seems they're pre-requisite to figure out step height.<br>
&lt;dael> astearns: koji is it alright ot  move on?<br>
&lt;dael> koji: Yeah. I'll re-read the discussion.<br>
&lt;dael> astearns: I wouldlike to see progress. I'll see what I can do to get that going. I think myles_ making the fonts will be a big help.<br>
&lt;Florian_> agreed<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/938#issuecomment-298968697 using your GitHub account
Received on Wednesday, 3 May 2017 16:47:32 UTC

This archive was generated by hypermail 2.3.1 : Monday, 23 October 2017 10:12:53 UTC