Open Bug 1686978 Opened 4 years ago Updated 1 year ago

Extend our printing WPT test harness to support pages-per-sheet and custom page ranges

Categories

(Core :: Printing: Output, task)

task

Tracking

()

People

(Reporter: dholbert, Assigned: jwatt)

Details

I'd like to tests that exercise the actual printing pipeline (printing to PDF rather than print-preview), testing the "pages per sheet" and "custom print range" functionality.

WPT tests seem like the best framework for this, since they use actual print-to-PDF pipeline, and they can be given new features (e.g. to specify pages-per-sheet or custom print range), via meta tags.

I'm not sure the tests themselves could be shared upstream yet, since the precise pages-per-sheet behavior/layout isn't standardized, as far as I'm aware. (particularly when it's not an exact fit, e.g. for 2 and 6 pages per sheet) So I might start the actual tests in a Mozilla-specific tests directory like https://searchfox.org/mozilla-central/source/testing/web-platform/mozilla/tests

Some link references for when I start working on this:
https://github.com/web-platform-tests/rfcs/blob/master/rfcs/print_test.md
https://searchfox.org/mozilla-central/source/testing/marionette/print.js

Note, I'm hoping this will let me test bug 1686494 (which currently I don't think is possible to test).

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

Some link references for when I start working on this:
https://searchfox.org/mozilla-central/source/testing/marionette/print.js

Followup: looks like I didn't use a perma-link here; and this^ file has moved twice since I filed this bug, first in bug 1693993 and then later in bug 1723137. It currently lives at https://searchfox.org/mozilla-central/rev/a8bd595d93203a7e836f4160a458c976b1232143/remote/shared/PDF.jsm (now using a perma-link :)) and I believe I referenced it here because it seems to be what we use for actually generating the PDFs for print-style WPT tests. (Specifically the print.printToFile function.)

Assignee: nobody → jwatt
You need to log in before you can comment on or make changes to this bug.