202549 - Mozilla does not update the HKCR\htmlfile key

Status: RESOLVED EXPIRED

(SeaMonkey :: UI Design, defect)

Description

[Antony Mawer]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030412
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4b) Gecko/20030412

A number of applications on Windows use the method outlined in the following
MSDN Q&A to detect the default browser:

http://msdn.microsoft.com/msdnmag/issues/01/01/c/default.aspx

While this may not be the best way of detecting the default browser, it is one
that is in use by mIRC at the least, and given that it's listed in this article,
is likely used by other applications. Timeless commented in bug 119095 that the
general preference was to change the .htm[l] associations to the applications
own key, however maybe setting Mozilla as the default browser should update the
HKCR\htmlfile key as well?

Reproducible: Always

Steps to Reproduce:
1. Run mIRC
2. Double click a URL

Actual Results:  
Internet Explorer opens.

Expected Results:  
Mozilla should open.

By modifying the default value of the following registry key:

HKEY_CLASSES_ROOT\htmlfile\shell\open\command

and setting it to:

D:\INTERNET\MOZILLA\MOZILLA.EXE -url "%1"

(or your favourite Mozilla location), mIRC then launches Mozilla to open URLs.

Comment 1

[Matthias Versen [:Matti]]

.

Comment 2

[Vidar Haarr (not reading bugmail)]

Just a reminder that being the default browser and the default handler for an
extension is not the same thing.

That's why we've got Edit->Preferences->Advanced->System.

Comment 3

[Antony Mawer]

To clarify that (re: comment 2), according to Preferences -> Advanced -> System,
I have Mozilla associated with all the listed file types (including HTML files)
with the exception of .bmp and .ico files.

Comment 4

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state.

If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way.
If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar).
If no action happens within the next few months, we move this bug report to an EXPIRED state.

Query tag for this change: mass-UNCONFIRM-20090614

Comment 5

[Robert Kaiser]

MASS-CHANGE:
This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago.

Because of this, we're resolving the bug as EXPIRED.

If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component.

Query tag for this change: EXPIRED-20100420