202829 - "Please enter a valid host name" when selecting Account Settings panels

Status: RESOLVED EXPIRED

(SeaMonkey :: MailNews: Account Configuration, defect)

Description

[Ninoschka Baca]

Trunk build 2003-04-18: Mac 10.1.5
Trunk build 2003-04-21: WinXP

Overview: In a new profile, cancel out of the Account Wizard dialog. Open
Account Wizard again to create an account. In Account Settings try to select any
of the panels and it reports the above error.

Steps to reproduce:
1. In a new profile open Mail
2. Cancel the Account Wizard dialog, select Exit
3. From the 3-pane , open the Account Settings dialog
4. Select the Add Account button so the Account Wizard appears
5. Progress through the dialogs to create an account and it eventually shows the
account in the Account Settings dialog.
6. Try to select one of the panels in the Account Settings dialog (i.e. Server
Settings)

Actual Results: It reports "Please enter a valid host name". Exit out of the
Account Setting dialog, reopen the Account Settings dialog and now you can
select a panel without the error occuring. The data in each panel also looks
correct.

Expected Results: No error should appear. It should just display the settings
for the panel selected.

Additional Information:
I found this bug in a new profile where I attempted to create a first account
and decided to cancel its creation on the last Account Wizard dialog. Then
completed the creation of another account which then displayed the Account
Settings dialog. After selecting any of the panels (Server Settings, Copies &
Folders etc...), it reported "Please enter a valid host name".

Comment 1

[Ninoschka Baca]

Marking nsbeta1. This does not occur in Netscape 7.02.

Comment 2

[Samir Gehani]

adt: nsbeta1-

Comment 3

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

mass re-assign.

Comment 4

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

[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