Conflict between different versions of XULRunner?

[jonmmorgan]

WebConnect seems to work fine with my two test applications (one the WebConnect test app, one my Python bindings test app). However, when I tried to integrate it into my app (again in Python) I found that HTTP requests were being routed to the version of Firefox I had open rather than opening in the WebConnect browser. I was using the same version of XULRunner as my Python test app (1.9.2) and initialising it in the same way. My Firefox is 3.6, and so should have a private build of XULRunner 1.9.2 underlying it, but even so it seems a bit strange that it would do that with one WebConnect app and not another.

Have you had any experience with this kind of thing? If so, are there any known fixes?

[jerry_mouse]

If you open the http requests from Windows shell (open, double clicking, or by execute wxShellExecute ...) then it will certainly be passed to the application that has registered to handle http protocol.
Other that these cases, I don't have any idea.

[jonmmorgan]

Yes, and I presume it is somehow executing it through the shell, but what I am calling is webcontrol.OpenURI('http://someurl.com'). The same behaviour happens for webcontrol.SetContent('http://someurl.com', '<my HTML document>').

I don't yet need the OpenURI() case, and I work around the SetContent() case by creating a new protocol with a dummy protocol handler which is only used by SetContent() [nsIWebBrowserStream requires a URL to be passed in so that it can resolve relative URLs]. But I would just be curious to know what's going on, since I can't quite see how it's working.