Closed
Bug 418024
Opened 17 years ago
Closed 2 years ago
message in separate tab or standalone window needs to show read and star status
Categories
(Thunderbird :: Message Reader UI, defect)
Thunderbird
Message Reader UI
Tracking
(Not tracked)
RESOLVED
WONTFIX
People
(Reporter: wsmwk, Unassigned)
References
Details
(Keywords: ux-control, ux-userfeedback)
Attachments
(1 file)
3.92 KB,
image/png
|
Details |
without icon in the standalone windows, you don't know if typing an "S" will assign or remove starred status from a message.
Reporter | ||
Comment 1•17 years ago
|
||
FWIW, messages "read" status is also not indicated in standalone window
Flags: wanted-thunderbird3?
Reporter | ||
Comment 2•15 years ago
|
||
/driving me crazy/
Component: Mail Window Front End → Message Reader UI
QA Contact: front-end → message-reader
Changed summary to reflect both
-tabs and standalone win
-read and star
if the case to separate them, excuse. At least tab and standalone are pretty much same case and solution if we talk about the header area. Wether is read and/or star, that is another issue. Some bugs are on priority also for this kind of case.
add dep to reader enh bug
Blocks: msgreadertracker
Summary: standalone message window needs to show star status icon → message in separate tab or standalone window needs to show read and star status
Reporter | ||
Comment 4•15 years ago
|
||
agree 100% on all points. will wait to see whether the issues need to be split into another bug.
Comment 5•15 years ago
|
||
Is this a regression, or did this happen in Tb2 also?
Reporter | ||
Comment 6•15 years ago
|
||
Not a regression. Star has never been shown. The more I use standalone window, the more not-minor this issue becomes.
Severity: minor → normal
Comment 8•14 years ago
|
||
I'd love to see this, too. The "shift+M" to mark unread status and "M" to mark read being separated was a useful workaround to not knowing the current state, but that apparently didn't last long. Explicitly showing the state would remove the guesswork about what the toggle version will do.
Comment 9•14 years ago
|
||
How about something like the following:
* Indicate read/unread through boldface on the subject (this would mean that
subjects would typically be *un*bold, however)
* Indicate starred messages with a star after (before?) the subject
* To eliminate confusion with the email address stars, turn those into little
people, a la the address book/composer
Reporter | ||
Comment 10•12 years ago
|
||
(In reply to Jim Porter (:squib) from comment #9)
> How about something like the following:
>
> * Indicate read/unread through boldface on the subject (this would mean that
> subjects would typically be *un*bold, however)
might be problematic for some people? (I'm not one)
> * Indicate starred messages with a star after (before?) the subject
> * To eliminate confusion with the email address stars, turn those into little
> people, a la the address book/composer
yes on all counts
Keywords: ux-control,
ux-userfeedback
Reporter | ||
Comment 11•12 years ago
|
||
Updated•2 years ago
|
Severity: normal → S3
Reporter | ||
Comment 12•2 years ago
|
||
The message reader is being largely rebuilt for version 115. So this issue is will not be fixed for the current version 102.
If the problem exists in version 115 when it becomes available in July please file a new bug. You can also evalute the rebuilt reader in 3-4 weeks by trying a beta build.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WONTFIX
You need to log in
before you can comment on or make changes to this bug.
Description
•