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

[bugs at horde.org]

DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/9432
------------------------------------------------------------------------------
  Ticket             | 9432
  Updated By         | Michael Slusarz <slusarz at horde.org>
  Summary            | Unable to mark messages as "read" in the dynamic view
  Queue              | IMP
  Version            | Git master
  Type               | Bug
  State              | Feedback
  Priority           | 1. Low
  Milestone          |
  Patch              |
-Owners             |
+Owners             | Michael Slusarz
------------------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2011-01-18 02:14) wrote:

> 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 (?)