- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 08 Nov 2018 00:37:31 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `what happens to block margins that aren't between block-level boxes?`, and agreed to the following: * `RESOLVED: define that margin collapsing between first or last child behaves same as between sibling children` * `RESOLVED: republish CR of Break L3 with this change` <details><summary>The full IRC log of that discussion</summary> <dael> Topic: what happens to block margins that aren't between block-level boxes?<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/3073<br> <dael> fantasai: This was the one issue open on fragmentation. dbaron suggested we can resolve<br> <dael> fantasai: What happens to margins...we have def when breaking between siblings, but not if you break before the first sibling or after the last.<br> <dael> fantasai: Typically you don't break there, you break before or after parent. You're only allowed to break there if there's a gap. If there's just extra space after layout you can break<br> <dael> fantasai: Proposed is do same as break at siblings. Truncate margins if forced, don't if unforced.<br> <dael> fantasai: Where that shows up is if you are in a multicol and you hae a much of stuff that breaks. You can tell if you truncated margin b/c height of multicol will be different if margin is there<br> <dael> Rossen_: Behavior sounds reasonable. This is what dbaron is proposing.<br> <dael> Rossen_: Other opinions?<br> <dbaron> yeah, sounds good to me... though not sure that it's what I was proposing<br> <dael> fantasai: He jsut wanted a definition. not sure if he wanted a specific one<br> <dael> dbaron: I don't think I was proposing something. sgtm<br> <dael> Rossen_: Objections to define that margin collapsing between first or last child behaves same as between sibling children ?<br> <dael> RESOLVED: define that margin collapsing between first or last child behaves same as between sibling children<br> <dael> fantasai: That's in L4, I'll edit into L3 then republish with that<br> <dael> Rossen_: Yes<br> <dael> florian: L3 is CR<br> <dael> fantasai: We resolved to publish already. There's just this one issue made sense to close it<br> <dael> Rossen_: Obj to republish CR of Break L3 with this change?<br> <dael> RESOLVED: republish CR of Break L3 with this change<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3073#issuecomment-436830228 using your GitHub account
Received on Thursday, 8 November 2018 00:37:33 UTC