Start Menu position is not good if replacing existing installation.

RESOLVED INCOMPLETE

Status

--
minor
RESOLVED INCOMPLETE
16 years ago
9 years ago

People

(Reporter: Gilles.Gravier, Unassigned)

Tracking

Trunk
x86
Windows XP

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

16 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021212
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021212

If one installs Mozilla over a previous install, then the installer should
automatically suggest the folder of the start menu where the previous Mozilla
was started from. I.E. I launch mine from Network\Mozilla ... this is what
should be offered as default choice if I replace a previous version already
installed to use this as the start menu.

Reproducible: Always

Steps to Reproduce:
1. Install Mozilla over a previous version (I did : over 1.2.1)
2.
3.

Actual Results:  
The default folder to have in the start menu was Mozilla instead of my existing
Network\Mozilla

Expected Results:  
Offered Network\Mozilla instead of Mozilla
Confirmed on wxp - 3/27 debug build.

This would only work if Mozilla was left in the originally installed location. 
Unless we searched the start menu, we wouldn't know where the icons were moved 
to. In this case, they should know how to remove them on their own and us 
doing it could cause problems.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Product: Browser → Seamonkey

Updated

13 years ago
QA Contact: bugzilla → general

Comment 2

9 years ago
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
Status: NEW → UNCONFIRMED
Assignee: dveditz → installer

Comment 3

9 years ago
old XPFE installer is dead, please REOPEN if it still happens with new NSIS-based SeaMonkey 2 installers.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.