Do we actually need the tab, or just the document? If its the latter, can we just keep the document around invisibly?
Andreas On Feb 25, 2013, at 10:14 PM, Zack Weinberg <za...@panix.com> wrote: > https://bugzilla.mozilla.org/show_bug.cgi?id=650960 seeks to replace the > existing print progress bars with something that isn't app-modal. Ignore > musings in the description and first few comments about getting rid of them > entirely and/or waiting for bug 629500. 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. However, the way this is implemented now is > inconvenient (it's been shoehorned into the nsIWebProgressListener interface, > which is not really fit for the purpose, and it involves some really icky > [that's a technical term] back-and-forth between C++ and JS) and app-modal > anything is Just Wrong. > > The existing patches in the bug have been vetoed because doorhanger > notifications aren't even universally available within Firefox, never mind > other applications. I am not aware of any universal alternative, and I know > very little about XUL. I *think* that the low-level approach in the bug, of > firing special chrome events at the window (plus some docshell goo to do the > actual close suppression), is still viable, and I think doorhangers are > appropriate for this when they're available. But I would like some help > figuring out what a good universal-backstop *receiver* of those chrome events > would look like, both in UX terms and implementation-wise. > > Thanks, > zw > _______________________________________________ > dev-platform mailing list > dev-platform@lists.mozilla.org > https://lists.mozilla.org/listinfo/dev-platform _______________________________________________ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
