1917145 - Firefox honors forced pagebreaks (page-break-before:always) between out-of-flow content and in-flow content (that's at the top-of-page), unlike Chrome

Status: RESOLVED DUPLICATE of bug 1772396

(Core :: Printing: Output, defect)

Description

[Daniel Holbert [:dholbert]]

Attachment: testcase 1

STR:

1. Load attached testcase.
2. Print-preview (or print)

ACTUAL RESULTS:
Two pages of output, with "ELEMENT #2" at the top-left of second page.

EXPECTED RESULTS:
One page of output, "ELEMENT #2" at the top-left of first page.

Chrome gives EXPECTED RESULTS.
Firefox and WebKit (epiphany) give ACTUAL RESULTS.

The question is whether page-break-before:always should force a break if the only thing that we've seen so far is some out-of-flow content. Chrome says no, Firefox/WebKit say yes. The site in Bug 1907822 happens to expect the Chrome behavior.

Comment 1

[Daniel Holbert [:dholbert]]

Hmm, this might be a version of bug 1772396. The presence/absence of the abspos "Element #1" doesn't actually seem to matter in this testcase -- we put Element #2 on page 2 regardless of whether that abspos element is there.

So I think really Element #2's forced pagebreak should be propagated to its parent (since it's the first [non-abspos] child), and that happens all the way up the tree, to the outermost box, which then doesn't have any previous-sibling to break before, and hence we don't end up page-breaking.