Taking discussion from IRC with :roc offline: > jviereck> roc: hi. I was thinking about adding a `abort()` function to the > PrintState that is passed to the mozPrintCallback. Calling this > function > will dismiss the printing process. For PDF.JS this is required if rendering > one of the pages fails. What do you think about it? > roc> jviereck: why would you want to abort just because you couldn't render a > page? > roc> why not just render the page as a big red cross or something and carry > on printing other pages?
Failing on one page is bad enough. Imagine the user starts the print job, goes to the printer and the printout looks correct at the first spot. But later he notice, something is missing that he depends on it. Also, printing red crosses might be very expensive for the user and therefore he'd like to know if something went wrong. As the abortion is programatic, the printing can get aborted, the developer notifies the user that something went wrong during printing and might give him the option to reprint but skip the failing page. Roc, what's your feeling about the proposed `abort()` now? Best, Julian _______________________________________________ dev-tech-layout mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-layout
