"get msgs" shouldn't have dropdown menu if there's only one account

RESOLVED EXPIRED

Status

SeaMonkey
MailNews: Message Display
--
enhancement
RESOLVED EXPIRED
17 years ago
8 years ago

People

(Reporter: Hakon, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

17 years ago
The "get msgs" button shouldn't have a dropdown menu if there's only one mail
account. Yet it does.
jglick?  What do you think about this?
Status: UNCONFIRMED → NEW
Ever confirmed: true

Updated

17 years ago
OS: Windows ME → All
QA Contact: esther → sheelar

Comment 2

17 years ago
I don't think its harmful having the dropdown when only one account is setup. 
Nice enhancement, but not critical. Moving to Future for now.
Target Milestone: --- → Future

Updated

16 years ago
QA Contact: sheelar → stephend

Comment 3

16 years ago
*** Bug 197901 has been marked as a duplicate of this bug. ***

Comment 4

15 years ago
*** Bug 194609 has been marked as a duplicate of this bug. ***
Product: Browser → Seamonkey

Updated

13 years ago
Assignee: sspitzer → mail
Assignee: mail → nobody
QA Contact: stephend → message-display
Target Milestone: Future → ---

Comment 5

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

Comment 6

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