Open Bug 1828792 Opened 2 years ago Updated 1 year ago

Save to PDF is not printing all pages (abspos fragmentation?)

Categories

(Core :: Printing: Output, defect, P3)

Firefox 112
defect

Tracking

()

People

(Reporter: sopor, Unassigned)

References

(Blocks 1 open bug)

Details

Attachments

(1 file)

Steps to reproduce:

Open this page: https://www.banber.com/banber/6374be9b2ee0e200077ec156 and try to Save to PDF.
The site is a bit slow, but I have waited for all pages to load before i try to print it to PDF.
I have tried other web browsers too and there all the pages will get saved to PDF as it should.

Actual results:

Only the two first pages shows text/pictures and the rest are blank.
It is not only the print preview that show two pages with text/images on. If i save it to a PDF, it will be the same result.

Expected results:

All pages should have text and pictures as the web page I'm trying to "print" have.

The Bugbug bot thinks this bug should belong to the 'Core::Printing: Output' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.

Component: Untriaged → Printing: Output
Product: Firefox → Core

The severity field is not set for this bug.
:emilio, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(emilio)

It seems everything that doesn't display is absolutely positioned basically. Ting-Yu do you know if we have a bug on file for this kind of issue?

Severity: -- → S2
Status: UNCONFIRMED → NEW
Ever confirmed: true
Flags: needinfo?(emilio)
Priority: -- → P3
Summary: Save to PDF is not printing all pages → Save to PDF is not printing all pages (abspos fragmentation?)

Err, see above.

Flags: needinfo?(aethanyc)

(In reply to Emilio Cobos Álvarez (:emilio) from comment #3)

It seems everything that doesn't display is absolutely positioned basically. Ting-Yu do you know if we have a bug on file for this kind of issue?

Bug 267029 is all about abspos printing, and layout.display-list.improve-fragmentation=true doesn't help in this case.

Blocks: 267029
Flags: needinfo?(aethanyc)

This needs a reduced testcase, ideally, but it's probably a version of Bug 267029.

Also, fortunately/unfortunately this is not a regression (or not a recent one); I confirmed that I can repro on Nightly 2020-01-01.
(Adjusting to S3 after discussing with emilio in triage; I think the S2 classification was on the assumption that it was recently-introduced breakage.)

Severity: S2 → S3

With the attached testcase 1, print-previewed on US Letter sized paper, Firefox shows me 10 pages of output, but most pages are blank (aside from the box-shadow "border" around the content area). The last word I see is "Parameter" at the top of page 2 (the only word on that page).
Chrome shows me 13 pages of output with content on most pages (except the last one which is just some ending decorations/box-shadow).

So it looks like all of the missing elements here are position:absolute and are inside of an overflow:hidden or overflow:auto container. That combination seems to cause content not to print, if it's on a page after the first page.

I'm not sure whether or not we've already isolated this situation as being problematic in another bug report somewhere. I've got a reduced testcase locally that I generated when looking at a similar issue with Google Docs, which I think is essentially bug 1816345.

You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: