<?xml version="1.0" encoding="UTF-8"?> 
<?xml-stylesheet href="https://dev.horde.org/themes/horde//default/feed-rss.xsl" type="text/xsl"?> 
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"> 
 <channel> 
  <title>advance upon &quot;Mark as...&quot; broken</title> 
  <pubDate>Thu, 09 Apr 2026 20:04:45 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/6715</link> 
  <atom:link rel="self" type="application/rss+xml" title="advance upon &quot;Mark as...&quot; broken" href="https://bugs.horde.org/ticket/6715/rss" /> 
  <description>advance upon &quot;Mark as...&quot; broken</description> 
 
   
   
  <item> 
   <title>When you select &#039;Mark as [attribute]&#039; while reading email, i</title> 
   <description>When you select &#039;Mark as [attribute]&#039; while reading email, it does not move to the next message to continue browsing. Instead, it remains on the same email. This prevents fluid browsing and requires the redundant action of clicking the next message arrow after a message has been read and marked for later use.</description> 
   <pubDate>Sat, 17 May 2008 12:32:29 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6715#t45321</link> 
  </item> 
   
  <item> 
   <title>Is this really more often than not going to be a &quot;next-messa</title> 
   <description>Is this really more often than not going to be a &quot;next-message&quot; type action? I&#039;d say about half the time I mark a message I&#039;m not done with it, or at least I don&#039;t want the next message.</description> 
   <pubDate>Sun, 18 May 2008 23:44:09 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6715#t45356</link> 
  </item> 
   
  <item> 
   <title>But we should be consistent with all message actions. And th</title> 
   <description>But we should be consistent with all message actions. And the user already has the choice to return to the mailbox or change to the next message after an action.</description> 
   <pubDate>Sun, 18 May 2008 23:51:29 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6715#t45357</link> 
  </item> 
   
  <item> 
   <title>Flags are often like undelete, though - when we undelete a m</title> 
   <description>Flags are often like undelete, though - when we undelete a message, we stay on that message.</description> 
   <pubDate>Sun, 18 May 2008 23:58:02 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6715#t45358</link> 
  </item> 
   
  <item> 
   <title>In the version we&#039;re coming from (4.0.5), &quot;Mark as...&quot; advan</title> 
   <description>In the version we&#039;re coming from (4.0.5), &quot;Mark as...&quot; advanced the message.   I&#039;d be happy with a preference.</description> 
   <pubDate>Mon, 19 May 2008 02:34:08 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6715#t45362</link> 
  </item> 
   
  <item> 
   <title>&gt; Flags are often like undelete, though - when we undelete a</title> 
   <description>&gt; Flags are often like undelete, though - when we undelete a message, 

&gt; 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.</description> 
   <pubDate>Mon, 19 May 2008 07:58:49 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6715#t45365</link> 
  </item> 
   
  <item> 
   <title>&gt;&gt; Flags are often like undelete, though - when we undelete </title> 
   <description>&gt;&gt; Flags are often like undelete, though - when we undelete a message,

&gt;&gt; we stay on that message.

&gt;

&gt; That would be inconsistent too then, IMO. All message actions 

&gt; consider the preference to return to the mailbox at the moment, which 

&gt; is what I use. So they should all either stay at the current message 

&gt; or proceed to the next, consistently, if that preference is turned 

&gt; 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 &quot;how would I implement this if we didn&#039;t have to reload the page&quot; (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&#039;t personally feel this is a pref item.</description> 
   <pubDate>Mon, 19 May 2008 19:29:26 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6715#t45382</link> 
  </item> 
   
  <item> 
   <title>&gt; I disagree with this statement.  Explicitly setting flags </title> 
   <description>&gt; I disagree with this statement.  Explicitly setting flags on a 

&gt; message is different than message actions IMHO.  If I look at this 

&gt; from the perspective of &quot;how would I implement this if we didn&#039;t have 

&gt; to reload the page&quot; (i.e., how would I implement in DIMP) - flagging 

&gt; messages would be something done in the background without changing 

&gt; the page.  Deleting/moving/copying is something when you do when you 

&gt; are done working with the message, so moving to another 

&gt; message/returning to mailbox is ok.



Alright, you outvoted me. As I said, I don&#039;t use this personally anyway, so my opinion is not too strong about it.



&gt; And I don&#039;t personally feel this is a pref item.



No, please not.</description> 
   <pubDate>Mon, 19 May 2008 23:28:46 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6715#t45389</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
