Tickets :: [#9432] Unable to mark messages as "read" in the dynamic view

6.0.0-beta1

7/4/25

Summary	Unable to mark messages as "read" in the dynamic view
Queue	IMP
Queue Version	Git master
Type	Bug
State	Resolved
Priority	1. Low
Owners	slusarz (at) horde (dot) org
Requester	wrobel (at) horde (dot) org
Created	12/07/2010 (5323 days ago)
Due
Updated	01/18/2011 (5281 days ago)
Assigned	12/08/2010 (5322 days ago)
Resolved	01/18/2011 (5281 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch	No

01/18/2011 09:23:46 PM	Michael Slusarz	Comment #6 State ⇒ Resolved	Reply to this comment
Yes - the issue is with multiple message selection - there's not a tremendously clean way of handling this in that case. Resolved by using Mark/Unmark for multiple message selection and using 'Mark' only when dealing with a single message.

01/18/2011 09:23:08 PM	Git Commit	Comment #5	Reply to this comment
Changes have been made in Git for this ticket: ~~Request #9432~~: Better context menu UI for setting/removing flags http://git.horde.org/horde-git/-/commit/25e35e391de3bff99e5a447bd1aeadfe345f957f

01/18/2011 07:14:13 AM	Michael Slusarz	Comment #4 Assigned to Michael Slusarz	Reply to this comment
But I have to admit that I would expect the one or the other user to have similar problems as this double negation is maybe not what every one would expect. This has been changed with the flag changes pushed within the last month. Is there a specific reason to split into "Mark as/Unmark as"? My expectation would be that the client only offers the markers that are actually available for a given message. Or a set of messages. But things become undeniable more difficult if the user selected several messages at the same time. Yes - the issue is with multiple message selection - there's not a tremendously clean way of handling this in that case. I would not be against having a single 'Mark As...' submenu, and then having checkmarks (or an equivalent UI element) indicating which flags are currently set - selecting a flag would toggle that flag. One drawback of this approach is that the UI between dimp and imp would not parallel each other - in IMP there is not really a clean way of doing this without listing both Mark and Unmark. But maybe we don't care about UI continuity between the different displays (?)

12/08/2010 04:55:27 AM	Gunnar Wrobel	Comment #3	Reply to this comment
Concerning "unread/unseen": That was an imprecise translation as I was looking at the german version of the client. Sorry for that. The 'Unmark as...' > 'Unseen' works. But I have to admit that I would expect the one or the other user to have similar problems as this double negation is maybe not what every one would expect. Is there a specific reason to split into "Mark as/Unmark as"? My expectation would be that the client only offers the markers that are actually available for a given message. Or a set of messages. But things become undeniable more difficult if the user selected several messages at the same time.

12/08/2010 12:16:48 AM	Michael Slusarz	Comment #2 State ⇒ Feedback	Reply to this comment
First, I don't see an 'Unread' option, I only see an 'Unseen' option (unseen is the correct nomenclature to use pursuant to RFC 3501). Second, we have an 'Unmark as...' > 'Unseen' option. I would rather not have BOTH Mark as 'Unseen' and Mark as 'Read' (actually, should be 'Seen' to be consistent with the RFC). The intent is that every option in the 'Mark As' menu should have a corresponding action in the 'Unmark' As menu.

12/07/2010 05:38:34 AM	Gunnar Wrobel	Comment #1 Priority ⇒ 1. Low Type ⇒ Bug Summary ⇒ Unable to mark messages as "read" in the dynamic view Queue ⇒ IMP Milestone ⇒ Patch ⇒ No State ⇒ Unconfirmed	Reply to this comment
Right-clicking on an unread message only offers "Mark as -> Unread". The expectation would be that the menu offers to mark such a message as "read". While this is an insignificant problem when selecting a single message it would be nice if it would be possible to mark many messages as "read" at the same time.