<?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>Don&#039;t dim signatures in quoted text</title> 
  <pubDate>Fri, 10 Apr 2026 14:49:33 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/4299</link> 
  <atom:link rel="self" type="application/rss+xml" title="Don&#039;t dim signatures in quoted text" href="https://bugs.horde.org/ticket/4299/rss" /> 
  <description>Don&#039;t dim signatures in quoted text</description> 
 
   
   
  <item> 
   <title>With today&#039;s dimsignature changes in HEAD, my unquoted signa</title> 
   <description>With today&#039;s dimsignature changes in HEAD, my unquoted signature is no longer dim.  Quoted signatures are dim though.</description> 
   <pubDate>Wed, 16 Aug 2006 21:28:39 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/4299#t23064</link> 
  </item> 
   
  <item> 
   <title>Your issue is bogus.  The algorithim for dimming signatures </title> 
   <description>Your issue is bogus.  The algorithim for dimming signatures recently changed from dimming everything below the first signature line to dimming everything below the last signature line.  It has nothing to do with quoted vs. unquoted.  The new algorithim makes more sense because it won&#039;t result in an entire message being dimmed if the signature appears on top.  Not to start a holy war, but it is definitely preferred etiquette to quote under previous text, so the user&#039;s signature should *always* appear at the bottom of the message.



However, your message does bring up another issue - namely, we shouldn&#039;t be dimming signatures in quoted text anyway if just for the simple fact we start mixing closed/unclosed div/span tags and the page won&#039;t render properly.  i.e., in this case, pseudocode looks like this:



&lt;div class=&quot;quoted1&quot;&gt;

&lt;div class=&quot;quoted2&quot;&gt;

 HTML

&lt;span class=&quot;signature&quot;&gt;

 Signature

&lt;/div&gt;

&lt;/div&gt;

&lt;/span&gt;



This is a severe limitation with the current Text_Filter scheme since each filter doesn&#039;t (and can&#039;t) know if a previous filter has inserted div/span tags that may intersect the current text.  Yuck.



Possible solution - we have to do signature dimming in the highlight quote filter.  This would ensure we weren&#039;t setting a signature span across quoted div&#039;s.</description> 
   <pubDate>Thu, 17 Aug 2006 14:34:53 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/4299#t23131</link> 
  </item> 
   
  <item> 
   <title>As far as I can tell, we need to combine some filter algorit</title> 
   <description>As far as I can tell, we need to combine some filter algorithms into a single call or else we will run into issues with improperly closed tags.  But this can&#039;t be done until Horde 4 since it will break BC.</description> 
   <pubDate>Tue, 26 Dec 2006 06:04:09 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/4299#t27789</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in Git for this ticket:

Bug #4299: F</title> 
   <description>Changes have been made in Git for this ticket:

Bug #4299: Fix dimming signatures when mixed with quoted text

http://git.horde.org/diff.php/framework/Text_Filter/lib/Horde/Text/Filter/Dimsignature.php?rt=horde-git&amp;r1=a4821dba3cebdd907a36635ce22b9569ce35e32b&amp;r2=85505a2a7397637aacfb9150f1b17d1a57618a7c
http://git.horde.org/diff.php/framework/Text_Filter/package.xml?rt=horde-git&amp;r1=0a1dd0cd19b9adc33aea4d4f137b4d6b0aef4e8f&amp;r2=85505a2a7397637aacfb9150f1b17d1a57618a7c</description> 
   <pubDate>Tue, 13 Oct 2009 00:47:22 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/4299#t56254</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
