Re: [csswg-drafts] [css-multicol] allow percentages for `column-gap`

The CSS Working Group just discussed ``allow percentages for `column-gap` ``, and agreed to the following resolutions:

* `RESOLVED: Add this to L1 and mark as at-risk.`

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: allow percentages for `column-gap`<br>
&lt;dael> Florian: WE resolved 4 years ago to allow column-gap to take %. Given that it's now, is that L1 or L2?<br>
&lt;dael> Rossen: Didn't we take the opposite for grid-gap?<br>
&lt;dael> Github topic:<br>
&lt;dael> Florian: I don't remember<br>
&lt;dael> jensimmons: We resolved grid-gap to take %<br>
&lt;dael> Rossen: If we're in alignment there's no controversy. They should be aligned.<br>
&lt;dael> Florian: Behavior is not unexpected. Q is where do we spec it.<br>
&lt;rachelandrew> grid-gap % is marked as risk in CR<br>
&lt;dael> Florian: We'll have to redo L1 CR, but we could do it there. Not sure there's  impl.<br>
&lt;dael> Rossen: I would say add as at-risk and then pass it to L2. I'm fine with that. Just more process &amp; editorial work. Other way is push to L2 now and if impl pick it  up we can bring it back.<br>
&lt;dael> fantasai: It's trivial to edit and to impl compared to making so other stuff in columns work. I think L1 and at-risk is fine.<br>
&lt;dael> Rossen: That's fine. Leave this in multi-col L1 and mark i t as at-risk.<br>
&lt;dael> Florian: put it in L1.<br>
&lt;dael> RESOLVED: Add this to L1 and mark as at-risk.<br>
&lt;dael> Rossen: That's the hour. Thanks everyone.<br>
&lt;Rossen> trackbot, end meeting<br>

GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at using your GitHub account

Received on Wednesday, 10 May 2017 17:04:56 UTC