892718 - Only the first page of a container of divs is being printed; Subsequent pages are empty.

Status: RESOLVED DUPLICATE of bug 546559

(Core :: Print Preview, defect)

Description

[Tom]

Attachment: badfirefox.pdf

User Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:22.0) Gecko/20100101 Firefox/22.0 (Beta/Release)
Build ID: 20130618035212

Steps to reproduce:

Go to the site:
http://mleibman.github.io/SlickGrid/examples/example11-autoheight.html

Select Print Preview in the browser.




Actual results:

Notice that the preview only shows the first page of data.  Subsequent pages are there, but there is no data on it.


Expected results:

4 pages of data should appear.  The entire table should be seen.

I attached a pdf of the table.  This functionality works in IE and Chrome.

Comment 1

[:Gijs (he/him)]

Attachment: Cache tabsintitlebar values in a JSM.

Comment 2

[:Gijs (he/him)]

Today's tip: don't get the bug number wrong in bzexport. :-\

Comment 3

[Wayne Mery (:wsmwk)]

This still reproduces in currently nightly

Comment 4

[Daniel Holbert [:dholbert]]

Yeah, this looks like absolutely positioned text ending up on the wrong page. Each of the "grid" rows is position:absolute (and the "grid" is position:relative to make it an abspos containing block).

Reduced testcase:

data:text/html,<div style="position:relative;height:30in"><div style="position:absolute;top:11in">HELLO CAN ANYONE SEE ME

Comment 5

[Daniel Holbert [:dholbert]]

(In reply to Daniel Holbert [:dholbert] from comment #4)
> Yeah, this looks like absolutely positioned text ending up on the wrong
> page.

And by "ending up on the wrong page", I mean "being positioned off the bottom of the first page, and hence not visible". Or something like that.

I'm pretty sure there's a bug filed on this already somewhere, but I can't find it at the moment.

Comment 6

[Wayne Mery (:wsmwk)]

bug 546559?

Comment 7

[Daniel Holbert [:dholbert]]

Maybe, though I'm not seeing content piled at the top of the second page (even if I add multiple lines to my data URL).

I'm not seeing any content at all, in print-preview.  So the results here don't quite match what's described on that bug.  That being said, I can't reproduce what's described on that bug anymore (I get different breakage now), so maybe it's all the same thing now.

Comment 8

[Daniel Holbert [:dholbert]]

Anyway, this does seem to hit the same underlying issue that the testcases on bug 546559 currently hit, so it probably makes sense to dupe to that bug.