On 2013-02-25 10:51 PM, Justin Dolske wrote:
Would it be helpful to fix this in two stages? EG, go ahead and land your backend changes now, but continue to use an app-modal dialog (which is driven by your new events). The new UI could then be investigated separately as an independent followup.
That is actually the thing I need help with. The current app-modal dialog is instantiated directly from C++ (via nsIPrintingPromptService) and exposes itself as a nsIWebProgressListener to the print engine. In the new model, the print engine just fires events at the chrome event handler for the document-being-printed's window. I was able to figure out how to field those events from browser.js and map them to doorhanger notifications (see https://bug650960.bugzilla.mozilla.org/attachment.cgi?id=627824 ) but I have no earthly idea where to put a backstop event handler that will be available to all XUL applications, or how to implement a backstop dialog box from JS.
zw _______________________________________________ dev-platform mailing list [email protected] https://lists.mozilla.org/listinfo/dev-platform
