W3C home > Mailing lists > Public > www-style@w3.org > February 2013

RE: [css3-break] Limiting break propagation to the fragmented flow

From: Andrei Bucur <abucur@adobe.com>
Date: Thu, 28 Feb 2013 23:11:07 +0000
To: Alan Stearns <stearns@adobe.com>, "www-style@w3.org" <www-style@w3.org>
Message-ID: <6E8E2AB3820BBC418FE7F934E849C9D01919680F45@eurmbx01.eur.adobe.com>
I also think it should be noted a propagated forced break does not apply if an unforced break already consumed the oportunity. For example, if there's an unforced break between the last child (that has break-after: always) of an element and the bottom border of it's containing element (e.g. the height of the container is taller than the fragmentainer) we stop propagating the break from the child to the parent beacuse the break occured naturally with the layout.

Thoughts?

Thanks,
Andrei.
________________________________________
From: Alan Stearns [stearns@adobe.com]
Sent: Thursday, February 28, 2013 2:34 PM
To: www-style@w3.org
Subject: [css3-break] Limiting break propagation to the fragmented flow

Section 4.1 notes that:

---
Since breaks are only allowed between siblings (1),
not between a box and its container,
a Œbreak-beforeš value on a first-child box
is propagated to its container.
Likewise a Œbreak-afterš value on a last-child box
is propagated to its container.
---

First, the (1) isn't clear to me - I'm assuming it refers to the mention
of 'siblings' in the Class 1 definition above.

Second, I think there should be one more sentence that notes that this
propagation stops at the fragmented flow boundary. If the first child of a
multicol element has break-before the break does not propagate to the
column or the multicol element. And if you have discontiguous elements
collected in a named flow, a break should not propagate to a container
outside of the named flow. Perhaps that's covered by the box/container
terminology, but in that case the break should never propagate to a region
box, either.

Thanks,

Alan
Received on Thursday, 28 February 2013 23:14:40 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:21:06 GMT