Closed
Bug 102518
Opened 23 years ago
Closed 18 years ago
Marking multiple messages as read sets all in selection to the toggled state of the first message
Categories
(SeaMonkey :: MailNews: Message Display, defect)
SeaMonkey
MailNews: Message Display
Tracking
(Not tracked)
People
(Reporter: mikepinkerton, Unassigned)
References
(Blocks 1 open bug)
Details
- open news so you have a mix of read and unread messages in a newsgroup
- select all the messages
- click 'mark' in the toolbar
Expected:
- all should be marked as read
Actual:
- if the first message is unread (bold), all messages are marked as read.
- if the first message is read (not bold), all messages are marked unread.
this seems rather broken, as the action i always expect from that button is to
mark things as read, regardless of what the first item I have selected is. i
usually end up hitting the button twice to mark everything as read, which sorta
defeats the purpose of having a convenient button.
this has been around for a long time, i'm sure there's another bug on it.
Comment 1•23 years ago
|
||
jglick, any opinions on this?
I would agree with author. The default behavior of the button is "Mark as Read".
So if any of the selected messages are Unread, I would expect it to mark them
all Read.
This is still a problem with dec14 commercial trunk build Mac OS X.
Seems to work okay on win98.
Comment 4•23 years ago
|
||
Somewhat related to this:
Menu item
Message/Mark/As Read
seems to be inconsistent:
1. If multiple messagea are selected (some are read, some are not), only one
state can be displayed (incorrectly) using the current checkmark implementation
2. What is the suggested way to mark messages unread (how I currently do it is
mark them read and unread, and/or opposite)?
Maybe there is to be a Mark As Unread and Mark As Read separate menuitems would
be a better choice.
Comment 5•22 years ago
|
||
Hello,
i would like to have such a "mark" button for my e-mails too. Often I know what
people want to tell me and will mark their messages as read to be able to see
next time what e-mails are really new then.
regards, F. Obermaier
In 1.2.1, "Mark as Read" used the tree selection lead (tail) as toggle
to set the state of all the rest of the messages. Since the reading
order is top-to-bottom (as the "Next unread Message" button), when
selecting a range, the last message is unread (due to the multiple
selections) and the "M"-command then toggles all to read. This is
what is expected.
Since 1.3b it is using the tree selection anchor (head), which is
wrong. It leads to having to click twice to get the messages marked
as read. The first selection one is normally read, and the "M"-command
then initially marks all "unread". This is inconsitent to the command
and to prior implementation.
Comment 7•21 years ago
|
||
happens on Mac OS X also. Moving over since mac classic is no longer supported.
OS: Mac System 9.x → MacOS X
Comment 8•21 years ago
|
||
This is also true in Windows ME version Mozilla/5.0 (Windows; U; Win 9x 4.90;
en-US; rv:1.5) Gecko/20030916
I would agree with comment #2 that if Mark as read is used all should be marked
as read. Rightg now it toggles depending on the first selected e-mail
Comment 9•21 years ago
|
||
This happens just the same way on Win2k. (and WinME according to comment above).
-> all/all
OS: MacOS X → All
Hardware: Macintosh → All
Comment 10•21 years ago
|
||
*** Bug 218572 has been marked as a duplicate of this bug. ***
Comment 11•20 years ago
|
||
*** Bug 251653 has been marked as a duplicate of this bug. ***
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•20 years ago
|
Assignee: sspitzer → mail
Updated•18 years ago
|
Status: NEW → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
You need to log in
before you can comment on or make changes to this bug.
Description
•