Closed Bug 198679 Opened 21 years ago Closed 21 years ago

mozilla/phoenix preferences are not correctly registered in WinXP

Categories

(SeaMonkey :: Preferences, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 202984

People

(Reporter: vedran, Assigned: bugs)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030321 Phoenix/0.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030321 Phoenix/0.5

When mozilla is installed on WinXP and associated as default browser, shortcut
link to preferences is not correctly associated in registry.

Reproducible: Always

Steps to Reproduce:
1. Install mozilla in WinXP.
2. Associate is as default browser.
3. Try to acess preferences from WinXP start menu.

Actual Results:  
Error running:
C:\PROGRA~1\MOZILLA.ORG\MOZILLA\MOZILLA.EXE-chrome
"chrome://communicator/content/pref/pref.xul"

Expected Results:  
Note the space before -chrome (this way it works)

C:\Program Files\mozilla.org\mozilla\mozilla.exe -chrome
"chrome://communicator/content/pref/pref.xul"

Also, all the other values in registry, like
HKEY_LOCAL_MACHINE\SOFTWARE\Clients\StartMenuInternet\MOZILLA.EXE\shell\open\command
for example, are in 8.3 format, so it shows PROGRA~1 instead of Program Files etc.
not bookmarks
Component: Bookmarks → Preferences
QA Contact: kasumi → sairuh
Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4a) Gecko/20030321 Phoenix/0.5

Reproduced too. Can someone confirm this bug?
*** Bug 199386 has been marked as a duplicate of this bug. ***
fixed in mozilla

*** This bug has been marked as a duplicate of 202984 ***

*** This bug has been marked as a duplicate of 202984 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
LOL... duplicate to the bug reported after that.
But I understand, because it was already fixed there.
v
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.