Open Bug 1372506 Opened 7 years ago Updated 2 years ago

Using PrintTargetSkPDF as default print-to-pdf backend

Categories

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

enhancement

Tracking

()

Tracking Status
firefox57 --- wontfix

People

(Reporter: bmo, Unassigned)

References

(Blocks 1 open bug)

Details

This is a follow-up from bug 1370488 comment 8.
We hit a failure in test case browser_DownloadPDFSaver.js and it was doing a print-to-pdf download testing from a single download task of a particular html document.

Originally print-to-pdf is supported by PrintTargetPDF which is powered by Cairo, now we have PrintTargetSkPDF(bug 1309272) and it makes more sense to have only one single backend to provide the function of saving document to pdf.
Blocks: pdf-printing
Depends on: 1309272
Jonathan, I might not be familar enough with your PrintTargetSkPDF implementation, does this bug make sense to you as a replacement of PrintTargetPDF to support print-to-pdf scenario?
Flags: needinfo?(jwatt)
Yes, the intention was to expand the PrintTargetSkPDF implementation to work on other platforms in addition to Mac, and work on making them robust enough that we can finally drop the cairo based PrintTargetPDF code. That was put on hold with the switch in focus to performance work.

The bugs blocking bug 1321689 cover getting the PrintTargetSkPDF code to a solid enough state that we could ship it on Mac. (No extensive testing has been done though, so it's unknown if there may be other issues lurking that may need to be fixed before shipping.) I guess this bug could be the overarching bug that covers shipping PrintTargetSkPDF for all platforms, including Mac.
Flags: needinfo?(jwatt)
Priority: -- → P3
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.