Bug 131214
| Summary: | [CSS Fragmentation] Break-before and break-after should propagate to the container in some cases | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Andrei Bucur <abucur> |
| Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> |
| Status: | NEW | ||
| Severity: | Normal | CC: | ahmad.saleem792, WebkitBugTracker |
| Priority: | P2 | Keywords: | AdobeTracked |
| Version: | 528+ (Nightly build) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Bug Depends on: | |||
| Bug Blocks: | 113050 | ||
Andrei Bucur
See: http://dev.w3.org/csswg/css-break-3/#break-between
"Since breaks are only allowed between siblings, not between a box and its container (see Possible Break Points), 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. (Conflicting values combine as defined below.) This propagation stops before it breaks through the nearest matching fragmentation context."
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Ahmad Saleem
Updated link - https://drafts.csswg.org/css-break-3/#break-propagation
"Since breaks are only allowed between siblings, not between a box and its container (see Possible Break Points), break values applied to children at the start/end of a parent are propagated to the parent, where they can take effect.
..."