Closed
Bug 191484
Opened 22 years ago
Closed 15 years ago
[mailviews] Customize View for recipients in my mailing list
Categories
(SeaMonkey :: MailNews: Message Display, enhancement)
SeaMonkey
MailNews: Message Display
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: nbaca, Unassigned)
References
(Blocks 1 open bug)
Details
Trunk biuld 2003-01-30: WinMe, Mac 10.1.3, Linux
Overview: When creating a customize view have an option to choose a list from an
address book.
Steps to reproduce:
1. Create a list in a local address book (i.e. personal address book, familylist)
2. In MailViews select the Customize option
3. Select the New button and try to define a view so:
the "Sender" "Is in my address book" "Personal Address Book/familylist "
Actual Results: The last dropdown box shows Personal Address Book. Click on the
down arrow and it displays the lists in a strange way. Lists appear horizontally
and some vertically.
Expected Results: It would be ideal if the user had a choice to:
a. Select the Personal Address Book, so all addresses would apply to the view
b. Select the Personal Address Book, click on a down arrow and see mailing lists
displayed one after the other so it would be easy to select a list (i.e.
famiylist) so only the addresses in the familylist would apply to the view.
If any of the people from my familylist send me a message then they will be the
only messages to appear in this view (i.e. mom, dad, brother, sister)
Note: This idea was also suggested by a user in a Usability Study.
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•20 years ago
|
Assignee: sspitzer → mail
Updated•16 years ago
|
Assignee: mail → nobody
QA Contact: laurel → message-display
Comment 1•15 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
•