Re: [csswg-drafts] [css-align][css-multicol] Gutter properties computed value

The Working Group just discussed `[css-align][css-multicol] Gutter properties computed value`, and agreed to the following resolutions:

* `RESOLVED: column-gap: normal computed value returns normal`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-align][css-multicol] Gutter properties computed value<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/2294<br>
&lt;dael> Rossen_: Summary is we have column gap normal value return as 0px for anything that's not a multi-column and 'normal' if it is a multicol<br>
&lt;dael> Rossen_: Issue raised by Igalia that get computed style where all browsers but edge return normal. Proposal was to make computed value to be normal everywhere.<br>
&lt;dael> Rossen_: The consensus on the issue seems to be normal computes as normal.<br>
&lt;dael> Rossen_: So I'm looking for feedback or other idea.<br>
&lt;dael> Rossen_: Should we just adopt proposed resolution or not change?<br>
&lt;dael> Rossen_: Does anyone care about this who is on the call?<br>
&lt;dael> tantek: Only thing I'd add is just +1 to Mats<br>
&lt;dael> Rossen_: What he's saying is common sense of not making style depend on layout and not make properties depend on other properties which is one of our guiding rules and I fully agree. Just curious on this issue.<br>
&lt;dael> rachelandrew: I agree with fantasai that people who care will specify anyway so if impl are happy to go with normal that makes sense.<br>
&lt;dael> Rossen_: I don't think we'll have a problem changing to normal. I think we're the only impl that returns 0. I'm assuming given all other impl return normal there shouldn't be a compat risk for us, or at least minimal.<br>
&lt;dael> tantek: Looking quick I didn't see a simple dom test to check current impl. I'd be curious to try it in other browsers to see if there is anything consensus-wise.<br>
&lt;dael> Rossen_: Right.<br>
&lt;dael> tantek: Can I request that before we resolve? To add a test to get information?<br>
&lt;dael> Rossen_: Absolutely. We don't have to resolve today. fantasai and florian are out. They and Sergio are active. I'm just looking for progress.<br>
&lt;dael> Rossen_: Sounds like we want examples and test cases to eval other impl.<br>
&lt;dael> tantek: At least to informt he decision better. SOunds like rough consensus but it's based on theoretical purity.<br>
&lt;dael> tantek: I'd like more concrete data.<br>
&lt;rego> http://w3c-test.org/css/css-align/gaps/column-gap-parsing-001.html<br>
&lt;dael> rego: THere's WPT tests for this. THat's why I realized Edge isn't returning normal and that's when I checked the specs.<br>
&lt;dael> tantek: Can you add a link to it?<br>
&lt;dael> rego: ^<br>
&lt;dael> tantek: Thanks.<br>
&lt;tantek> rego which of the tests?<br>
&lt;tantek> (of the 17)<br>
&lt;rego> the first one "Default column-gap is 'normal'"<br>
&lt;rego> in Edge it fails<br>
&lt;rego> I meant, it returns 0px<br>
&lt;dael> Rossen_: I see the same behavior as rego stated in the issue. In windows I see Edge report 0 and FF and Chrome return<br>
&lt;dael> Rossen_: 'normal'<br>
&lt;dael> tantek: There's 17 tests.<br>
&lt;dael> rego: First one is the one that fails<br>
&lt;dael> Rossen_: fwiw looking at IE I think we regressed this in edge unintentionally.<br>
&lt;dael> Rossen_: For the sake of argument this could be jsut a bug.<br>
&lt;dael> tantek: I see normal in FF &amp; Chrome<br>
&lt;rego> and Safari<br>
&lt;dael> Rossen_: Yeah. That's what I said. Normal everywhere, FF, Chome IE 11. Edge is only one that does 0.<br>
&lt;dael> tantek: Safari also.<br>
&lt;dael> tantek: Okay. That makes it pretty clear.<br>
&lt;dael> Rossen_: Going back to the issue, is this something we want to punt or do we feel there is enough understanding to resolve?<br>
&lt;dael> tantek: I think there's enough understanding.<br>
&lt;dael> tantek: If fantasai or anyone else has new information we can follow our normal proceedure.<br>
&lt;dael> Rossen_: fantasai supports normal to normal in the issue.<br>
&lt;dael> Rossen_: Objections to resolving that column-gap: normal computed value returns normal?<br>
&lt;dael> RESOLVED: column-gap: normal computed value returns normal<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2294#issuecomment-369313438 using your GitHub account

Received on Wednesday, 28 February 2018 17:19:17 UTC