Bug 1684952 Comment 15 Edit History

Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.

Thanks for following up on that. There must be some local flakiness around my printer (and/or some local print service) which was causing my occasional failures to print.

(In reply to Václav Trpišovský from comment #13)
> >robust way that works with pages-per-sheet
> 
> This should not be an issue since this is usually done on the driver's side.

Yeah, that's how we used to handle it; but with our new built-in print dialog, we have to offer a live print-preview of how the pages-per-sheet rendering is going to look, which means we have to implement it ourselves (which is what I've done in other bugs).
Thanks for following up on that. There must be some local flakiness around my printer (and/or some local print service) which was causing my occasional failures to print reversed page ranges from Chrome/Edge.

(In reply to Václav Trpišovský from comment #13)
> >robust way that works with pages-per-sheet
> 
> This should not be an issue since this is usually done on the driver's side.

Yeah, that's how we used to handle it; but with our new built-in print dialog, we have to offer a live print-preview of how the pages-per-sheet rendering is going to look, which means we have to implement it ourselves (which is what I've done in other bugs).

Back to Bug 1684952 Comment 15