rundll32 url.dll,FileProtocolHandler and "start.exe" to launch URL doesn't bring Mozilla to the front

RESOLVED WORKSFORME

Status

defect
RESOLVED WORKSFORME
15 years ago
11 years ago

People

(Reporter: bert690, Assigned: jag+mozilla)

Tracking

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

15 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6) Gecko/20040113

There are two common ways to launch the default browser in windows. One is the
"start.exe" command, the other is the "rundll32 url.dll,FileProtocolHandler"
command. Many Java applications for instance use these methods.  When internet
explorer is installed these commands properly load the page in IE and bring the
browser to the front of the screen. In contrast, if you are running Mozilla and
a mozilla window is *already open* but behind some other window, then these
commands will cause one of the mozilla windows to load the page, however the
window will not be brought to the front.

Reproducible: Always
Steps to Reproduce:
1. Set Mozilla as the default browser
2. Open up the Mozilla browser, but bring some other window(s) on top of it.
3. At a command prompt type "rundll32 url.dll,FileProtocolHandler [some http url]"
4. Witness that 
Actual Results:  
While the Mozilla window loads the page specified by [some http url], it does
not come to the front.


Expected Results:  
Mozilla window should load the page AND come to the front, just like IE does
when it is set as the default browser.


Happens under Win2000 as well as WinXP. Possibly others.
Product: Browser → Seamonkey
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
(Reporter)

Comment 2

14 years ago
Still reproducible in Mozilla 1.7.10, and still annoying!

Updated

14 years ago
Assignee: general → jag
Component: General → XP Apps
QA Contact: general

Comment 3

11 years ago
WFM using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.12) Gecko/20080201 SeaMonkey/1.1.8.  If this bug can be reproduced using a recent SeaMonkey build, feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.