Closed
Bug 199742
Opened 23 years ago
Closed 15 years ago
column pickers in mailnews and address book should allow serial selections
Categories
(SeaMonkey :: MailNews: Message Display, enhancement)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: pascalc, Unassigned)
Details
(Keywords: polish)
1 create a new profile
2 open address book, the 14 colmuns for fields are displayed by default
If you want to only show names and emails you will have to click on the column
picker widget 13 times and unselect each field one at a time. Extremely annoying
and time consuming. You have to do the same for mail columns and the adress book
selection window from a compose window. This is very clumsy and less efficient
than Netscape 4 or Outlook Express.
I think that what we should have is a similar drop down list which would allow
multiple selection and would have an OK button to validate the changes like :
+--------------------+
| x Email |
| x Screen name |
| x Company |
| x Nickname |
| x Additional Email |
| x Department |
| x Title |
| x etc. |
+--------------------+
| OK |
+--------------------+
Updated•22 years ago
|
Summary: column pickers in mailnews and address book should allow serial selections → column pickers in mailnews and address book should allow serial selections
Updated•21 years ago
|
Product: Browser → Seamonkey
Updated•20 years ago
|
Assignee: sspitzer → mail
Updated•17 years ago
|
Assignee: mail → nobody
QA Contact: esther → message-display
Comment 1•16 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 2•15 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
Closed: 15 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•