Closed Bug 2052162 Opened 17 days ago Closed 22 hours ago

Regression since 150b1: pdf printing with blank pages / wrong page breaks

Categories

(Core :: Printing: Output, defect)

Firefox 150
defect

Tracking

()

RESOLVED FIXED
154 Branch
Tracking Status
firefox-esr115 --- unaffected
firefox-esr140 --- unaffected
firefox-esr153 --- affected
firefox152 --- wontfix
firefox153 --- affected
firefox154 --- fixed

People

(Reporter: maxbritov, Assigned: emilio)

References

(Regression)

Details

(Keywords: regression)

Attachments

(5 files)

Attached image fff152.png

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:152.0) Gecko/20100101 Firefox/152.0

Steps to reproduce:

Opening electro document in edi provider.
Open preview and print:
FF 149 - 12 pages in preview
FF150b1..153b7 - 122 pages

Attached image fff152 another.png
Attached image fff149.png

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.
:jwatt, could you have a look please?

For more information, please visit BugBot documentation.

Flags: needinfo?(mozmail)

Thanks for the bug report! Unfortunately it looks like the affected URL is not publicly viewable. Is there any chance you can generate a testcase that reproduces the bug? The "SingleFile" extension might be useful as a way of turning the page that you're viewing into a testcase, if that page is appropriate for sharing (not sure) -- you can get that here https://addons.mozilla.org/en-US/android/addon/single-file/

If there's private data included in the testcase that's not suitable for posting publicly as an attachment on this bug, you're also welcome to send a testcase directly via email to me at dholbert@mozilla.com (if you're comfortable doing so) and I can try to construct a reduced testcase with all the content removed, and then I'll delete the email.

I also noticed you're using 16 pages-per-sheet -- I'm guessing that's just to make the bug easier to see in screenshots, right? (Or, does the bug specifically only happen when you're printing multiple pages per sheet?)

I have a couple of other ideas for threads to investigate (notably mozregression which might be a way to identify the change that caused the issue), but let's start with this set of questions for now. :) Thanks!

Flags: needinfo?(mozmail) → needinfo?(maxbritov)

(In reply to Daniel Holbert [:dholbert] from comment #5)

If there's private data included in the testcase that's not suitable for posting publicly as an attachment on this bug, you're also welcome to send a testcase directly via email to me at dholbert@mozilla.com (if you're comfortable doing so) and I can try to construct a reduced testcase with all the content removed, and then I'll delete the email.

Sent video as private email

Thanks, Maxim!

Maxim managed to construct a standalone testcase, shared privately -- and with that, I was able to bisect with mozregression and determine that this was a regression from this commit:
https://hg-edge.mozilla.org/integration/autoland/rev/1e396370701364d07e54fb4877df04835526d947 ("Bug 343048 - Get rid of ColGroup list")

I'll try to construct a shareable reduced testcase from Maxim's testcase later on today.

Flags: needinfo?(maxbritov) → needinfo?(dholbert)
Keywords: regression
Regressed by: 343048
Status: UNCONFIRMED → NEW
Ever confirmed: true

Set release status flags based on info from the regressing bug 343048

Attached file testcase 1 (reduced)

Here's a reduced testcase.

In Chrome and pre-regression Firefox, this gives me 6 pages in print-preview.
In post-regression Firefox, this gives me 78 pages (most of the pages being blank).

One other notable thing - this seems to be dependent on the fragmentation fallback codepath -- if I turn that off by toggling about:config pref layout.display-list.improve-fragmentation to false, then the issue goes away.

Flags: needinfo?(dholbert)

:emilio, since you are the author of the regressor, bug 343048, could you take a look? Also, could you set the severity field?

For more information, please visit BugBot documentation.

Flags: needinfo?(emilio)

table { overflow: hidden } works around the issue, indeed.

Only rowgroups should be considered. Also, there's a separate issue
where the Reflow() loop might've pushed some of the frames in mRowGroups
to the next continuation, but we'd still consider overflow for them.

Assignee: nobody → emilio
Status: NEW → ASSIGNED
Flags: needinfo?(emilio)
See Also: → 2055928
Regressions: 2055952

Created web-platform-tests PR https://github.com/web-platform-tests/wpt/pull/61380 for changes under testing/web-platform/tests

Test timeout (annotated in comment 15) is odd, but it might "just" be an instance of bug 1886588.

Reverted this because it was causing wpt failures in table-in-flex-overflow-print.html.

Flags: needinfo?(emilio)

Upstream PR was closed without merging

(In reply to Daniel Holbert [:dholbert] from comment #16)

Test timeout (annotated in comment 15) is odd, but it might "just" be an instance of bug 1886588.

Yes it is, but it got annotated in the wrong folder (testing/web-platform/tests rather than ../meta

Flags: needinfo?(emilio)
Status: ASSIGNED → RESOLVED
Closed: 22 hours ago
Resolution: --- → FIXED
Target Milestone: --- → 154 Branch

Upstream PR merged by moz-wptsync-bot

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

Attachment

General

Creator:
Created:
Updated:
Size: