1976450 - print, save as pdf, produces empty file (maybe triggered by "alpha" SVG mask-type?)

Status: RESOLVED DUPLICATE of bug 1970805

(Core :: Printing: Output, defect)

Description

[Rachel Evans]

Attachment: doc title here.html

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.15; rv:140.0) Gecko/20100101 Firefox/140.0

Steps to reproduce:

• Fresh new FF profile
• Open the attached HTML file
• Print
• Save to PDF
• Wait for the dialog to close

Actual results:

The file doc title here.pdf is created, but is empty (zero bytes long).

Expected results:

Either a valid PDF file should have been created, or a message should have been shown explaining that the save didn't work.

Comment 1

[BugBot [:suhaib / :marco/ :calixte]]

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.

Comment 2

[Rachel Evans]

This test file, by the way, is the result of me trimming down a page where I experienced the problem, down to a smaller problem space.

The yellow quadrilateral seen in the page was, in the original page, part of the Google Play logo for a "Get it on Google Play" link-to-app button. Somehow, it seems to be that quadrilateral that triggers the bug.

Comment 3

[Rachel Evans]

Attachment: with-mask-type-alpha.html

Simpler fail case

Comment 4

[Rachel Evans]

Attachment: with-mask-type-luminance.html

Simpler success case

Comment 5

[Rachel Evans]

The only difference between with-mask-type-alpha.html and with-mask-type-luminance.html is the mask-type style (and the document title).

alpha produces a 0-byte PDF. luminance produces a valid PDF.

Comment 6

[Jonathan Kew [:jfkthame]]

Thanks for the report, and particularly for reducing the example so thoroughly -- that's really helpful.

It looks like the failure here was recently fixed in bug 1970805 (expected to ship in Firefox 142), so current Nightly versions no longer have this issue. (I'm not certain the resulting rendering is necessarily correct, particularly for more complex cases, but at least it should generate a valid file.)