Closed
Bug 371217
Opened 18 years ago
Closed 14 years ago
need more appropriate indicator for non-displayed e-mail addresses
Categories
(Thunderbird :: Mail Window Front End, enhancement)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: mozillauser, Unassigned)
References
()
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.1) Gecko/20061204 Firefox/2.0.0.1
Build Identifier: 2.0.0.1
This is a "usability" issue.
Seems that Thunderbird needs a more appropriate way to indicate that there are more addresses (e.g., in the "To:" section) than are being displayed. I suggest a terminal comma-and-(hyperlinked-)ellipsis a the end of an incomplete list. See http://www.philipt.com/temp/mozilla/thunderbird/20070221/ for an illustration of exactly what I mean.
(Couldn't figure out how to add this image as an attachment to this "bug(/suggestion) report, which would seemingly be more appropriate in this case... someone feel free to add the graphic at that site as an attachment to this thread if you know how.)
Thanks in advance for your consideration of this (and my apologies if it's a dup; I couldn't find an exact match.)
Reproducible: Always
Steps to Reproduce:
1. Receive an e-mail with more addresses than will display (e.g., in the "To:" section);
2. Note that there's no clear contextual indication at the END of the list (which is the obvious place to look from a usability standpoint);
3. CAST YOUR VOTE FOR THIS FIX! :)
Actual Results:
no clear contextual indication at the END of the list (which is the obvious place to look from a usability standpoint) that there are more (undisplayed) addresses
Expected Results:
have a clear contextual indication at the END of the list (which is the obvious place to look from a usability standpoint) that there are more (undisplayed) addresses
Updated•17 years ago
|
Assignee: mscott → nobody
Comment 1•14 years ago
|
||
This should be fixed in 3.0+, since the end of the list now has a link that says "more".
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•