Olaf wrote:
Haven't looked at it yet. Functionality is the main issue now. I have
to make sure I can implement everything we need in time. Now I'm
working on creating new windows on demand (nsIWindowCreator). A HTML
page with target _new works like a charm, but JS alerts go horribly
wrong (I get two windows, and when I call alert again I get an
assertion).
Olaf,
You should look into nsIPromptService and implement these yourself.
I've had problems with the "Default" ones and so implemented these on my
app and it works a WHOLE lot better. I remember seeing some docs on
Mozilla.org/Developer on getting started in doing this.
Also, you will want to be sure your nsIWindowCreator is implemented
properly for multiple windows. If that is not implemented correctly, it
can cause problems probably not unlike you are having...and also when
the popup window is destroyed...make sure that you don't kill your whole
nsIWebBrowserChrome class when you close out the popup window. (I use a
window counter variable to keep track of how many windows I've got up
and close everything when my windows counter hits 0). Hope this helps!
Niky Williams
_______________________________________________
dev-embedding mailing list
[email protected]
https://lists.mozilla.org/listinfo/dev-embedding
