69372 - desktop settings set to wrong registry key

Status: RESOLVED EXPIRED

(SeaMonkey :: UI Design, defect)

Description

[ajbu]

Destop settings on Windows are set to the registry key 
HKEY_LOCAL_MACHINE\SOFTWARE\Mozilla\Desktop. After installing and running 
Mozilla,  there are two keys in HKLM\Software, 'Mozilla' and 'Mozilla.org'. 
This keyname should probably be build with dynamicly from the 
vendor/application name. This should also be moved from HKEY_LOCAL_MACHINE, as 
the user running Mozilla might not have the rights to edit HKEY_LOCAL_MACHINE 
on NT/Windows 2000.

This value is now hardcoded in nsWindowsHooksUtil.cpp

Comment 1

[sairuh (rarely reading bugmail)]

bill, should this go to the installer folx or you?

Comment 2

[timeless]

reporter: please include a spec url.

Sun java creates the following keys:
HKEY_*\SOFTWARE\JavaSoft
netbeans creates:
HKEY_CURRENT_USER\Software\netbeans.org\NetBeans IDE
sysinternals uses:
HKEY_CURRENT_USER\Software\Sysinternals\Tokenmon
HKEY_CURRENT_USER\Software\Systems Internals\Filemon
possibly HKEY_CURRENT_USER\Software\NTInternals\WinObj
winzip uses:
HKEY_CURRENT_USER\Software\Nico Mak Computing\WinZip
HKEY_CURRENT_USER\Software\WinZip Computing
hilgraeve has
HKEY_CURRENT_USER\Software\Hilgraeve Inc\HyperTerminal PE
HKEY_CURRENT_USER\Software\HyperSend
netscape smart download uses
HKEY_LOCAL_MACHINE\SOFTWARE\Nsda
active state uses
HKEY_LOCAL_MACHINE\SOFTWARE\ActiveState\ActivePerl
HKEY_LOCAL_MACHINE\SOFTWARE\ActiveState\ActivePython
[but there are also]
HKEY_LOCAL_MACHINE\SOFTWARE\Perl
HKEY_LOCAL_MACHINE\SOFTWARE\Python
wincvs uses
HKEY_CURRENT_USER\Software\WinCvs
HKEY_LOCAL_MACHINE\SOFTWARE\GNU\WinCvs 1.1
i think stardivision is staroffice
HKEY_CURRENT_USER\Software\StarDivision
microsoft probably owns
HKEY_LOCAL_MACHINE\SOFTWARE\Windows 3.1 Migration Status

fwiw, Sun Forte ~ (netbeans.org) NetBeans, Sun StarOffice ~ 
(openoffice.org) Open Office, AOL Netscape ~ (mozilla.org) Mozilla.

i'll install openoffice and see what it does.

--Using HKLM is often acceptable, especially when the admin makes association 
changes for the computer (as stored in HKLM).  We should probably always try to 
use HKLM and fall back to HKCU when rebuked.

Comment 3

[ajbu]

> reporter: please include a spec url.
What kind of spec url can I provide? Is there some Mozilla documentation about 
how this should work I am missing and could read?

To explain why I reported this: At first the settings where all in one key, 
Software\Mozilla\, but lately the installer has moved the keys used in 
installation/uninstall to Software\Mozilla.org\Mozilla\.
(This is actually the way dictated by Microsoft in the 'Application 
specifications for desktop applications' document 
http://msdn.microsoft.com/certification/downloads/Win2000AppSpec-Desktop.exe )


The application still uses Software\Mozilla, so the registry keys are now in 
two places.

I seems usefull to me that the keys are kept in one place with the same root.
(If you want to use the same keys for NS/Mozilla another key would make sense, 
but I don't think that is needed for the desktop-integration keys.)

My remark about HKLM can be ignored

Comment 4

[Chris McAfee]

over to law for a look.

Comment 5

[Keyser Sose]

Marking NEW.

Comment 6

[Bill Law]

Known issue that needs resolution.  We have to sort out Mozilla vs. brand
registry issues (and how to stop different Mozilla's from fighting to be
"default browser") and registry access issues ("installing" into HKLM when user
has access, HKCU when they don't, installer vs. app, etc.).

Comment 7

[Peter Trudelle]

->099

Comment 8

[Bill Law]

Spam: Moving out bugs that there is no time for.

Please note that some of these will hopefully be fixed in the course of fixing 
bug 59078.  I just can't commit to fixing them all.

Comment 9

[Robert Kaiser]

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 10

[Robert Kaiser]

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 11

[Robert Kaiser]

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 12

[Robert Kaiser]

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 13

[Robert Kaiser]

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 14

[Robert Kaiser]

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 15

[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