Add "Print on both sides" checkbox option to new print UI (duplex printing)
Categories
(Toolkit :: Printing, enhancement, P2)
Tracking
()
People
(Reporter: jwatt, Assigned: nordzilla)
References
(Depends on 1 open bug)
Details
(Whiteboard: [print2020_v84][old-ui-])
Attachments
(1 file, 1 obsolete file)
Bug 1651115 added nsIPrinter.supportsDuplex
that can be used to determine whether a printer supports duplex printing. (That may be made per-paper information in bug 1658394.) If nsIPrinter.supportsDuplex
is true, then we should expose this is the UI. The frontend code would set nsIPrintSettings.duplex
to one of kDuplexHorizontal
or kDuplexVertical
if duplex is supported, based on whether the user selects "Flip on long edge" or "Flip on short edge".
This is required for parity with the legacy UI and parity with Chrome.
Reporter | ||
Updated•4 years ago
|
Assignee | ||
Comment 2•4 years ago
|
||
Going to take a crack at this in an attempt to get somewhat familiar with the front-end code.
I'm expecting that new code here will be very similar to existing code.
Also, I've been working on the platform side of this functionality (Bug 1658394), so it seems like a good bug to start with.
Assignee | ||
Comment 3•4 years ago
|
||
Updated•4 years ago
|
Updated•4 years ago
|
Assignee | ||
Updated•4 years ago
|
Comment 4•4 years ago
|
||
(Moving to 84.)
Updated•4 years ago
|
Assignee | ||
Comment 5•4 years ago
|
||
NI'ing Emilio as per our conversation on Matrix, to see if he might have any insights into this intermittent leak until shutdown that is happening on macOS, triggered by the new test cases that this patch adds.
I've been trying to get to the bottom of it for some time now, with little luck so far.
Example:
Comment 6•4 years ago
|
||
I got this try run with all but the last of the duplex browser tests skipped, so the log is a bit easier to scan through:
Comment 7•4 years ago
|
||
I tried to repro this on Linux and no dice. Will try on Mac and see if I can poke a bit more.
Comment 8•4 years ago
|
||
I tried to repro on mac with a debug artifact build and couldn't either... Did about 6 runs of ./mach mochitest browser_print_duplex.js --verify
...
However per our discussion, TV doesn't necessarily block landing, so we might want to try to land it if it doesn't fail when ran in regular mochitests... If we do that it'd be nice to keep a bug on file to track why is this failing on TV.
I'd also be interested in knowing whether other printing tests fail similarly on verify...
Comment 10•4 years ago
|
||
Backed out for perma failures.
Log: https://treeherder.mozilla.org/logviewer?job_id=320922918&repo=autoland&lineNumber=1751
Backout: https://hg.mozilla.org/integration/autoland/rev/d6963d98cd379c66cc3b348a29e18a8e6d1bbb7d
Assignee | ||
Comment 11•4 years ago
|
||
I accidentally missed a line when resolving a merge conflict and it sneaked its way into that test. So sorry about that.
Comment 12•4 years ago
|
||
Comment 13•4 years ago
|
||
Updated•4 years ago
|
Comment 14•4 years ago
|
||
bugherder |
Updated•4 years ago
|
Comment 15•4 years ago
|
||
I retested everything using latest Nightly 85.0a1 and Firefox 84.0b3 on Windows 10 x64, Ubuntu 16.04 x64 and macOS 11.1. The "Print on both sides" checkbox option is displayed underneath the "Two-sided printing" section.
Description
•