Bug 106995 - [CSS Fragmentation] Break-after:always always on a box and break-before:always on the next box should collapse
Summary: [CSS Fragmentation] Break-after:always always on a box and break-before:alway...
Status: NEW
Alias: None
Product: WebKit
Classification: Unclassified
Component: WebCore Misc. (show other bugs)
Version: 528+ (Nightly build)
Hardware: Unspecified Unspecified
: P2 Normal
Assignee: Nobody
URL:
Keywords: AdobeTracked
Depends on:
Blocks: 113050
  Show dependency treegraph
 
Reported: 2013-01-16 02:15 PST by Andrei Bucur
Modified: 2014-02-03 11:59 PST (History)
3 users (show)

See Also:


Attachments
Test case (572 bytes, text/html)
2013-01-16 02:16 PST, Andrei Bucur
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Andrei Bucur 2013-01-16 02:15:42 PST
In the case of two sibling boxes, the first specifying break-after: always and the second break-before: always, there should be only one break generated and no empty fragmentainer.

"A forced break then occurs at (1) if, among the ‘break-after’ properties specified on or propagated to the earlier sibling box and the ‘break-before’ properties specified on or propagated to the later sibling box there is at least one with a forced break value.

When multiple forced break values apply to a single break point, they combine such all types of break are honored and no content-empty page boxes are generated, except for at most one content-empty page as may be required by the forced break values to position ensuing content on a specific type of page. When ‘left’, ‘right’, ‘recto’, and/or ‘verso’ are combined, the value specified on the latest element in the flow wins."
Comment 1 Andrei Bucur 2013-01-16 02:16:13 PST
Created attachment 182940 [details]
Test case