On 02/25/2013 04:57 PM, Bobby Holley wrote:
On Mon, Feb 25, 2013 at 1:28 PM, Benjamin Smedberg<benja...@smedbergs.us>wrote:
On 2/25/2013 4:14 PM, Zack Weinberg wrote:
The current thinking is that we need *some* indication that a print job
is in progress, because we need to prevent the user from closing the tab or
window until the print job has been completely handed off to the OS.
Why?
Is the user allowed to interact with the tab contents (potentially
modifying the DOM)?
We clone static copies of documents for print preview. We could potentially
do the same for normal printing, I'd think.
The work I've already done on printing is at a rather lower level; I
don't claim to understand fully how it works at the document/window/
shell level. But as far as I know, we do already clone a static copy of
the document for normal printing.
The only deep reason I can think of for keeping the tab around is that
under some operating systems, closing the last tab triggers application
shutdown, and it would probably violate expectations to delay that with
no user-visible indication of why. However, I expect that if I tried to
remove all the superficial reasons why we need to keep the tab around,
I'd discover that it's a giant mess.
Independent of all that, printing long documents can take tens of
seconds just to complete the handoff to the OS print queue (I've been
testing with the one-page HTML5 spec) and so I do think a user-visible
indication of progress is desirable.
zw
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
