- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Tue, 04 Jun 2019 20:18:48 +0000
- To: public-css-archive@w3.org
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> <fremy> Topic: where do we define column-gap<br> <astearns> github: https://github.com/w3c/csswg-drafts/issues/3641<br> <fremy> rachelandrew______: we define column-gap in multicol and box alignment<br> <fremy> rachelandrew______: authors were discussing how confusing that was<br> <fremy> rachelandrew______: I'd rather define column-gap in alignment, and just mention the specificities of column-gap for columns in multicol<br> <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> <fremy> AmeliaBR: we should consider REC progress though, so we don't get stuck<br> <fremy> fantasai: css-align is really close to REC, so I don't think that would be an issue<br> <fantasai> s/REC/CR/<br> <fremy> fantasai: the only remaining issue is baseline alignment<br> <fremy> fantasai: and we could move that to the next level<br> <fantasai> s/issue/significant source of issues/<br> <fremy> AmeliaBR: then that seems fine<br> <fremy> astearns: suggested edit is to add an heading to explain how column-gap works in multicol, but define in box-alignment only<br> <fremy> astearns: any objection?<br> <fremy> RESOLVED: add an heading to explain how column-gap works in multicol, but define in box-alignment only<br> <fremy> (and link between them)<br> <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