[Tickets #6715] Re: advance upon "Mark as..." broken

[bugs at horde.org]

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

Ticket URL: http://bugs.horde.org/ticket/6715
-----------------------------------------------------------------------
 Ticket             | 6715
 Updated By         | Michael Slusarz <slusarz at horde.org>
 Summary            | advance upon "Mark as..." broken
 Queue              | IMP
 Version            | 4.2-RC4
 Type               | Bug
 State              | Feedback
 Priority           | 1. Low
 Milestone          |
 Patch              |
 Owners             |
-----------------------------------------------------------------------


Michael Slusarz <slusarz at horde.org> (2008-05-19 15:29) wrote:

>> Flags are often like undelete, though - when we undelete a message,
>> we stay on that message.
>
> That would be inconsistent too then, IMO. All message actions
> consider the preference to return to the mailbox at the moment, which
> is what I use. So they should all either stay at the current message
> or proceed to the next, consistently, if that preference is turned
> off.

I disagree with this statement.  Explicitly setting flags on a message is
different than message actions IMHO.  If I look at this from the
perspective of "how would I implement this if we didn't have to reload the
page" (i.e., how would I implement in DIMP) - flagging messages would be
something done in the background without changing the page.
Deleting/moving/copying is something when you do when you are done working
with the message, so moving to another message/returning to mailbox is ok.

And I don't personally feel this is a pref item.