Re: [csswg-drafts] [css-multicol] Should we refer to definition of `column-gap` in Box Alignment? (#3641)

The CSS Working Group just discussed `where do we define column-gap`, and agreed to the following:

* `RESOLVED: add an heading to explain how column-gap works in multicol, but define in box-alignment only`

<details><summary>The full IRC log of that discussion</summary>
&lt;fremy> Topic: where do we define column-gap<br>
&lt;astearns> github: https://github.com/w3c/csswg-drafts/issues/3641<br>
&lt;fremy> rachelandrew______: we define column-gap in multicol and box alignment<br>
&lt;fremy> rachelandrew______: authors were discussing how confusing that was<br>
&lt;fremy> rachelandrew______: I'd rather define column-gap in alignment, and just mention the specificities of column-gap for columns in multicol<br>
&lt;fremy> florian: we kinda did the same thing for break properties, where they usually were defined in multiple places, and now we consolidated in css-break and we added notes to the other places<br>
&lt;fremy> AmeliaBR: we should consider REC progress though, so we don't get stuck<br>
&lt;fremy> fantasai: css-align is really close to REC, so I don't think that would be an issue<br>
&lt;fantasai> s/REC/CR/<br>
&lt;fremy> fantasai: the only remaining issue is baseline alignment<br>
&lt;fremy> fantasai: and we could move that to the next level<br>
&lt;fantasai> s/issue/significant source of issues/<br>
&lt;fremy> AmeliaBR: then that seems fine<br>
&lt;fremy> astearns: suggested edit is to add an heading to explain how column-gap works in multicol, but define in box-alignment only<br>
&lt;fremy> astearns: any objection?<br>
&lt;fremy> RESOLVED: add an heading to explain how column-gap works in multicol, but define in box-alignment only<br>
&lt;fremy> (and link between them)<br>
&lt;AmeliaBR> s/astearns: suggested/rachelandrew______: suggested/<br>
</details>


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

Received on Tuesday, 4 June 2019 20:18:50 UTC