<?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>Option to go straight to thread view</title> 
  <pubDate>Thu, 09 Apr 2026 21:18:36 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/5902</link> 
  <atom:link rel="self" type="application/rss+xml" title="Option to go straight to thread view" href="https://bugs.horde.org/ticket/5902/rss" /> 
  <description>Option to go straight to thread view</description> 
 
   
   
  <item> 
   <title>If you are viewing a mailbox in thread view, I would like op</title> 
   <description>If you are viewing a mailbox in thread view, I would like opening a message to open the entire thread, not just the single message.  That would save me another click to choose the thread view at that point.



I can see that not everyone would want this, so I would suggest this be turned on optionally in the configuration.

</description> 
   <pubDate>Mon, 19 Nov 2007 15:48:20 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5902#t38755</link> 
  </item> 
   
  <item> 
   <title>I want this too. The only issue that kept me from implementi</title> 
   <description>I want this too. The only issue that kept me from implementing this so far is, that I have no idea how to do it UI-wise.</description> 
   <pubDate>Wed, 21 Nov 2007 16:03:46 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5902#t38862</link> 
  </item> 
   
  <item> 
   <title>My initial thoughts were to have an icon over by the message</title> 
   <description>My initial thoughts were to have an icon over by the message status (attachment, high prioirity, etc) that would be clickable to open the whole thread, but that doesn&#039;t seem to really fit in with the purpose of those icons.  Maybe an icon just before the subject field and before the dotted line that ties the threaded messages together?  Perhaps that would only show up when viewing the mailbox in threaded view so it wouldn&#039;t be too obnoxious for people not viewing it as such.</description> 
   <pubDate>Wed, 21 Nov 2007 16:32:27 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5902#t38870</link> 
  </item> 
   
  <item> 
   <title>I committed some initial version to CVS, what do folks think</title> 
   <description>I committed some initial version to CVS, what do folks think?</description> 
   <pubDate>Wed, 21 Nov 2007 18:02:32 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5902#t38879</link> 
  </item> 
   
  <item> 
   <title>I&#039;m pretty unhappy with this. I was already bugged by the in</title> 
   <description>I&#039;m pretty unhappy with this. I was already bugged by the inconsistency of indenting threaded messages (when there are multiple top-level messages in a thread, they both have the same indenting as a reply in another thread); this introduces another variation. And I still really think that if we&#039;re going to do something like this we should take the cue from Gmail and show only one message in the list, with a link to the full thread.



I know there are technical challenges to doing that, but I think that&#039;s the way to go here.</description> 
   <pubDate>Wed, 21 Nov 2007 19:56:48 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5902#t38891</link> 
  </item> 
   
  <item> 
   <title>&gt; I&#039;m pretty unhappy with this. I was already bugged by the </title> 
   <description>&gt; I&#039;m pretty unhappy with this. I was already bugged by the 

&gt; inconsistency of indenting threaded messages (when there are multiple 

&gt; top-level messages in a thread, they both have the same indenting as 

&gt; a reply in another thread);



I had to get used to that too, but now I find it rather intuitive and actually more consistent  than the old behavior. Did I get something wrong?



&gt; this introduces another variation. And I



Why does it introduce a variation? It&#039;s the same for any thread and this little icon is the least intrusive solution I could come up with without rewriting the whole mailbox rendering which is out of the question at this moment. But of course I&#039;m open for better UI ideas.



&gt; still really think that if we&#039;re going to do something like this we 

&gt; should take the cue from Gmail and show only one message in the list, 

&gt; with a link to the full thread.



Yeah, that would be the ultimate goal, but is this intermediate solution really that bad? I&#039;m not attached to exactly this implementation, but I really want this feature, and I want to get it in before the RC1.</description> 
   <pubDate>Fri, 23 Nov 2007 00:17:11 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5902#t38919</link> 
  </item> 
   
  <item> 
   <title>&gt; I had to get used to that too, but now I find it rather in</title> 
   <description>&gt; I had to get used to that too, but now I find it rather intuitive and actually more consistent than the old 

&gt; behavior. Did I get something wrong?



If you look at the screenshot here, what I was talking about is the thread about Text_reST - both messages have the same indent level as the reply to the Turba address book thread.



&gt;&gt; this introduces another variation. And I

&gt;

&gt; Why does it introduce a variation?



Because threads with the link-to-thread image have a different indent level than either of the above possibilities. Also, you can see that the Text_reST thread has no link image, so that&#039;s a new inconsistency.



&gt; Yeah, that would be the ultimate goal, but is this intermediate solution really that bad? I&#039;m not attached to 

&gt; exactly this implementation, but I really want this feature, and I want to get it in before the RC1.



It is relatively unobtrusive, but it does catch the eye a little - also I would have no idea what it meant if I didn&#039;t know the code or use the mouseover, but icons are hard like that in general.



I think it&#039;s a half measure, but not bad enough to completely veto it. You did ask what others thought, so, my thoughts are on the table. :)</description> 
   <pubDate>Fri, 23 Nov 2007 04:51:53 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5902#t38925</link> 
  </item> 
   
  <item> 
   <title>I would prefer this didn&#039;t go into 4.2 either - if just beca</title> 
   <description>I would prefer this didn&#039;t go into 4.2 either - if just because I have plans to totally redo how we handle threading in future (5.0).  So having a feature that may only be in a single point release before disappearing again may not be the best.



As far as chuck&#039;s issue - I have *never* seen that issue before.  All of my threads with multiple top-level messages always appear completely left justified.  Is this something that has recently appeared with jan&#039;s changes?</description> 
   <pubDate>Fri, 23 Nov 2007 07:15:45 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5902#t38928</link> 
  </item> 
   
  <item> 
   <title>You both convinced me, I reverted it.



&gt; As far as chuck&#039;s</title> 
   <description>You both convinced me, I reverted it.



&gt; As far as chuck&#039;s issue - I have *never* seen that issue before.  All 

&gt; of my threads with multiple top-level messages always appear 

&gt; completely left justified.  Is this something that has recently 

&gt; appeared with jan&#039;s changes?



No, I have always seen this too. But as I already said, I got used to it and for me it now makes sense, because you still easily spot threads even if there isn&#039;t a single common parent message. You can&#039;t identify threads with messages on the same level otherwise.</description> 
   <pubDate>Fri, 23 Nov 2007 11:13:16 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5902#t38938</link> 
  </item> 
   
  <item> 
   <title>&gt; No, I have always seen this too. But as I already said, I </title> 
   <description>&gt; No, I have always seen this too. But as I already said, I got used to 

&gt; it and for me it now makes sense, because you still easily spot 

&gt; threads even if there isn&#039;t a single common parent message. You can&#039;t 

&gt; identify threads with messages on the same level otherwise.



That wasn&#039;t what I was talking about.  I was talking about the extra space to the left of these lines for these kind of threads.  But this was due to the thread link code and has been fixed by your revert.



BTW, I agree with Jan about the threads - after all I was the one who created that display in the first place :)  To this day, nobody else has provided a way to represent this kind of thread - with multiple bottom-level messages - any better.</description> 
   <pubDate>Mon, 26 Nov 2007 23:27:27 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5902#t39046</link> 
  </item> 
   
  <item> 
   <title>Essentially a duplicate of the revived #3278</title> 
   <description>Essentially a duplicate of the revived #3278</description> 
   <pubDate>Sun, 09 Nov 2008 03:27:32 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/5902#t50538</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
