54625 - username on prefilled accounts should not be editable

Status: RESOLVED WONTFIX

(SeaMonkey :: MailNews: Account Configuration, defect)

Description

[Warren Harris]

I've stumbled on this bug several times, and only just now realized what's going on:

- Create a new profile, launch and activate with your netcenter account
- Bring up mail
- The first time it brings up the Account Manager dialog and asks you for your
name and email address.

>>> I typed in my name and netscape email address ([e-mail]) erasing
the netcenter one ([e-mail]) because I never use the
netcenter one.

- Click the next button after filling this out, and you get a final page in the
dialog where the only button is "Finish". Click "Finish" and now you're screwed.
The dialog changes what I typed, "[e-mail]" to "[e-mail]"
which doesn't belong to me. This is wrong and confusing.

One of 2 things should probably happen here instead: Either the dialog should
not let me edit the email address if it's determined to just get a username for
my netcenter account, or if I do edit it to be a different email address from
what it originally had, it should go through the entire account setup process,
and make that my default account ([e-mail]) instead of keeping the
netcenter one as the default.

Very confusing as it stands.

Comment 1

[Alec Flett]

well, I think there are two issues:
1) the @netscape.net is only supposed to appear in the static text area next to
the <textfield> - this is a dupe of a bug I already have
2) I think now that the username should not be editable either.

since 1) is already a dupe, let's make this bug for 2)

Comment 2

[Alec Flett]

massive reassign of account manager bugs -> sspitzer
please feel free to put me back on the CC if you have any questions/comments

Comment 3

[Ninoschka Baca]

Adding mail3 as keyword. Making the email address not editable is a good idea. 
It will make it more clear that the dialog is specific for netscape.net 
accounts.

Comment 4

[(not reading, please use [e-mail] instead)]

more bugs to racham.

Comment 5

[scottputterman]

marking nsbeta1+ and moving to mozilla0.8.

We need to make it so that prefilled accounts aren't editable but that new
accounts are editable.

Comment 6

[scottputterman]

moving to mozilla1.0

Comment 7

[scottputterman]

marking nsbeta1-

Comment 8

[(not reading, please use [e-mail] instead)]

mass re-assign.

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]

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

Comment 15

[Tony Mechelynck [:tonymec]]

The @netscape.net special-coding went away with Netscape Mail IIUC.

I'm leaving this as-is.

Comment 16

[Karsten Düsterloh]

(Marking WONTFIX to get it rid from the UNCO/EXPI radar.)