News account name "user on" prefix appears then vanishes

RESOLVED EXPIRED

Status

--
minor
RESOLVED EXPIRED
17 years ago
9 years ago

People

(Reporter: jim.avera, Unassigned)

Tracking

Trunk
x86
Linux

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
If a new news server account is created from the "Account Status"
dialog from an existing account, then the new account name
displayed in the left panel of the Account Settings dialog
initially appears as "username at <server-name>".

However, the "username at " prefix does not appear when
the account is displayed in the main news/mail window, and
if the Account Status dialog is dismissed and later recalled
the prefix is no longer present there either.

Comment: Since the behavior is inconsistent, and there is not really enough
room to see the news account with the prefix in the (default sized)
panel, I think it would be better to never display this prefix.
But if it is displayed, then it should probably be displayed
consistently whenever the new account name is shown.

To reproduce:
1. Tasks->Mail & Newsgroups
2. (if no existing news server accounts exist, then create one).
3. In the main news/mail screen,
   Click on an existing news account in the left box.
4. Click "View settings for this account" (Account Settings pops up).
5. Click on "New Account" inside the Account Settings dialog.
6. Fill out the form to create a new NEWS account 
   (it can have a bogus server hostname).
7. After clicking Finish in the account creation sequence, notice that
   the new account appears as "user on ..." in the left panel of
   the Account Settings dialog.
8. Click OK.
9. Click on the newly created account in the left panel of the main window
   (which does not show the "user on ..." prefix).
10. Observe that the "user on..." prefix has disappeared in the
   Account Status left panel.

Comment 1

17 years ago
Confirmed linux 2002032221
Status: UNCONFIRMED → NEW
Ever confirmed: true
mass re-assign.
Assignee: racham → sspitzer
Product: Browser → Seamonkey

Updated

14 years ago
Assignee: sspitzer → mail
QA Contact: nbaca

Comment 3

9 years ago
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

Comment 4

9 years ago
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

9 years ago
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
Status: UNCONFIRMED → RESOLVED
Last Resolved: 9 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.