- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Thu, 04 May 2017 05:03:13 +0000
- To: public-css-archive@w3.org
An added benefit of defining things this way is that it would make clear that the bottom margin of a element immediately preceding the spanner and the top margin of an element immediately following are supposed to be preserved be rather than discarded since they would be adjoining a forced break. We would probably need to add normative prose supporting the claim made in example 25 that when the spanning element itself is the first thing after an unforced page break, its top margin is truncated. I guess we could do that by clarifying that the forced break is on the place holder left in flow after taking the spanning element out of flow, not on the spanning element itself. I guess something like this: > all: The element is taken out of flow, and spans across all columns of the nearest multicol ancestor in the same block formatting context. A placeholder is left in its place, and a <a>forced break</a> is introduced as if 'break-before: column' had been specified on the placeholder. Content in the normal flow that appears before <a>forced break</a> is automatically balanced across all columns before the <a>spanner</a>, and the rest resumes after the <a>spanner</a> -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1072#issuecomment-299097552 using your GitHub account
Received on Thursday, 4 May 2017 05:03:19 UTC