Thank you and God Bless <><
Greg Marine
I would have thought this would just work, with the default window creator in
xpfe...
You can certainly hook up an nsIWindowProvider, I would think.
-Boris
No chrome package registered for chrome://navigator/content/navigator.xul
Anyone know what I should do? Am I asking the wrong group?
Thank you and God Bless <><
Greg Marine
>I've messaged around with prefs. for this, but I keep getting the following warning when clicking links which would open in a new window:
>
>No chrome package registered for chrome://navigator/content/navigator.xul
>
>Anyone know what I should do?
>
You have two options:
1. You can change the browser.defaultChromeURL pref. This should
point to a XUL window with a <browser type="content-primary">
element in which the new page can be opened.
2. You can create an nsIBrowserDOMWindow object. This fields all
window opening calls, and allows you full control over what to do
with them (load in the existing window or a new tab perhaps).
--
Warning: May contain traces of nuts.
you can use a preference to tell XULRunner the XUL window to use when
opening webcontent windows:
pref("browser.chromeURL", "chrome://path/to/window.xul");
Prism does the same thing.
God Bless <><
Greg Marine