If Embedding Xulrunner 2.0 it requests for a new window with a browser inside if e.g. a web page opens a simple alert box. It calls nsIWindowCreator2::CreateChromeWindow2 and renders the dialog box content into the returned nsIWebBrowserChrome.
That works all fine, but inside the returned nsIWebBrowserChrome only the URL of the dialog content (chrome://global/content/commonDialog.xul) is displayed, but without content (like i just enter the chrome url in the firefox 4.0 browser). It seems that the parameters for the XUL get lost somewhere. If using Xulrunner 1.9.2 all works fine. (Xulrunner 1.9.2 uses nsIPromptService2 to display alert boxes, but other XUL-dialogs like the certificate error dialog works well) Does anybody know what changed inside the Xulrunner framwork? Debugging Xulrunner where it looses the parameters seems to be very elaborate. Greetings, Dominik -- View this message in context: http://old.nabble.com/Embedding-Xulrunner-2.0%3A-CreateChromeWindow2-%28e.g.-if-Xulrunner-Requests-a-Window-for-a-simple-Alert-Box%29%3A-chrome%3A--global-content-commonDialog.xul-rendered-without-content-tp31441873p31441873.html Sent from the Mozilla - Embedding mailing list archive at Nabble.com. _______________________________________________ dev-embedding mailing list [email protected] https://lists.mozilla.org/listinfo/dev-embedding
