290556 - goto-url-external

Status: RESOLVED INVALID

(Other Applications :: ChatZilla, defect)

Description

[Michael (GoodWill)]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

Re: goto-url-external

Unable to open two or more different link in the same browser process.
It seems nsIExternalProtocolService like to launch separate processes.
See below.



Reproducible: Always

Steps to Reproduce:
1. You will need two different browsers. One that is default browser in the OS
(lets say mozilla suite and a second one that is NOT a DEAULT browser (lets say
firefox with chatzilla installed). 
2. close the default OS browser (moilla suite), close all the windows make sure
its not running at all.
3. Start the browser with chatzilla installed on it.
4. Set Link opening to goto-url-external, set it for click so it is easier to use.
5. in the *client window type in /echo http://www.mozilla.org then /echo
http://www.google.com
6. Click the first link and wait until it loads in the external/default browser
(mozilla suite).
7. Now click the second link and wait. 

Actual Results:  
A Mozilla Suite Profile chooser pops up. This happens because it think the
original profile is thought to be in use.



Expected Results:  
What should have happen: the second link should have opened in the already
opened mozilla suite window.


Simple Work around: drag an drop.

Comment 1

[Michael (GoodWill)]

this will nto b reproducable for IE as default browser, cause IE does nto care
about separately launched browser processes.

Comment 2

[James Ross]

Yes, the external protocol crap does spawn new processes - that is exactly how
any app that launches URLs works. 

If you get a profile choice dialog with Mozilla, you need to unset the
enviroment variable MOZ_NO_REMOTE which you must have set manually yourself;
alternatively, you may be on a platform where Mozilla does not automatically
remote with itself (it didn't used to on Linux), which is not our (CZ) problem,
and there is likely an existing bug for it.