On 22 Feb., 04:08, Boris Zbarsky <[EMAIL PROTECTED]> wrote: > fi wrote: > > As a first attempt I had my listener registered in the command-line > > handler of my XULRunner application > > Registered how?
Exactly as Michel suggested: var uriLoader = Components.classes["@mozilla.org/uriloader; 1"].getService(Components.interfÂaces.nsIURILoader); var contentListener = Components.classes["@your-component-id;1"]. createInstance(Components.interfaces.nsIURIContentListener); uriLoader.registerContentListener(contentListener); In the command-line handler, before the first call the windowwatcher.windowOpen(); (If I remember right... I do not have access to the code right now) Well, there may have been a slight difference, can this be relevent? I think I used [...] var contentListener = Components.classes["@your-component-id; 1"].createInstance( ); [...] QI was called twice, once for the creation of the component and then, I think, when it was registered. Afterwards no other method of my listener was called. > > > Then I had my listener registered in an iframe of my first page > > You don't really want to do that... That would mess with the existing > URIContentListener chain the browser sets up. > > -Boris That is good news. -Andreas _______________________________________________ dev-tech-xpcom mailing list [email protected] https://lists.mozilla.org/listinfo/dev-tech-xpcom
