122143 - profile naming inconsistent

Status: RESOLVED EXPIRED

(SeaMonkey :: Startup & Profiles, enhancement)

Description

[Gabor Liptak]

From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)
BuildID:    2002012708

1. Clear all profiles for Mozilla using the Profile Manager
2. Shutdown Mozilla
3. When Mozilla starts, a profile named "default" is created
4. Then if "new profile" is clicked, a profile named "Default User" is created

Reproducible: Always
Steps to Reproduce:
1. Clear all profiles for Mozilla using the Profile Manager
2. Shutdown Mozilla
3. When Mozilla starts, a profile named "default" is created
4. Then if "new profile" is clicked, a profile named "Default User" is created

Actual Results:  Using multiple names

Expected Results:  Using one name

Comment 1

[Grace Bush]

Not sure this is bug- think it is as designed- however reporter has a point, 
marking as enhancement and confirming

Comment 2

[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 3

[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