<?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>address suggestion popup becomes unusable as you add more recipients</title> 
  <pubDate>Fri, 10 Apr 2026 13:16:49 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/7074</link> 
  <atom:link rel="self" type="application/rss+xml" title="address suggestion popup becomes unusable as you add more recipients" href="https://bugs.horde.org/ticket/7074/rss" /> 
  <description>address suggestion popup becomes unusable as you add more recipients</description> 
 
   
   
  <item> 
   <title>When composing a message using IE6 or IE7, the address look </title> 
   <description>When composing a message using IE6 or IE7, the address look up suggestion pop-up starts to move left as you add recipients.   Pretty much by the time the field (To, Cc, Bcc) starts to fill up and start scrolling existing entries to the left, the pop up will move to the left as well, eventually moving beyond the boundaries of the composition window.</description> 
   <pubDate>Wed, 16 Jul 2008 15:05:12 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7074#t47590</link> 
  </item> 
   
  <item> 
   <title>Confirmed.</title> 
   <description>Confirmed.</description> 
   <pubDate>Wed, 16 Jul 2008 18:15:26 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7074#t47592</link> 
  </item> 
   
  <item> 
   <title>This is fixed if using the latest dev version of prototypejs</title> 
   <description>This is fixed if using the latest dev version of prototypejs.  I glanced at the code, but there have been so many changes to the positioning functions that there is little/no chance we would be able to do a clean patch to 1.6.0.2.  Don&#039;t know if this bug is nasty enough to upgrade to the latest dev version (?)</description> 
   <pubDate>Tue, 22 Jul 2008 04:57:56 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7074#t47698</link> 
  </item> 
   
  <item> 
   <title>I would say no, unless someone is coming up with a stripped-</title> 
   <description>I would say no, unless someone is coming up with a stripped-down patch the exactly fixes this issue.</description> 
   <pubDate>Wed, 23 Jul 2008 15:28:09 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7074#t47739</link> 
  </item> 
   
  <item> 
   <title>Then this is probably better marked as stalled, since the ne</title> 
   <description>Then this is probably better marked as stalled, since the next version of prototypejs will fix this.</description> 
   <pubDate>Tue, 29 Jul 2008 03:28:21 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7074#t47867</link> 
  </item> 
   
  <item> 
   <title>We worked around the problem by adding code in the fixIEOver</title> 
   <description>We worked around the problem by adding code in the fixIEOverlapping function in imp/js/controls.js to calculate the proper absolute position for the autocompletion div.  This file has been stripped and renamed to autocomplete.js (as well as other changes to other files for other fixes) which is why we didn&#039;t submit this for use.  Anyway, here&#039;s the code if it&#039;s useful:



fixIEOverlapping: function() {

    Position.clone(this.update, this.iefix, {setTop:(!this.update.style.height)});

    this.iefix.style.zIndex = 1;

    this.update.style.zIndex = 2;

    //*** BEGIN Change ***

    // Need to set the left position bceause IE shifts it to the left for each added address

    var e = document.getElementById(&#039;to&#039;);

    var n = e.offsetLeft;

    var p = e.offsetParent;

    while(p&amp;&amp;p.tagName!=&#039;BODY&#039;)

    {

        n+=p.offsetLeft;

        p=p.offsetParent;

    }

    this.update.style.left = n;

    //*** END Change ***

    Element.show(this.iefix);

  }



Not elegant but it does work.  Sounds like the problem will go away in the near future anyway.

</description> 
   <pubDate>Wed, 20 Aug 2008 16:23:46 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7074#t48315</link> 
  </item> 
   
  <item> 
   <title>Thinking about this more - this is *really* broken behavior.</title> 
   <description>Thinking about this more - this is *really* broken behavior.  I think this is blocking on IMP 4.2.1.  Given the hack solution given in the previous comment, we are better off using the latest pre-1.6.0.3 version of prototypejs (especially since it provides some other fixes that are useful elsewhere).</description> 
   <pubDate>Fri, 22 Aug 2008 06:01:59 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7074#t48358</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in CVS for this ticket:

http://cvs.h</title> 
   <description>Changes have been made in CVS for this ticket:

http://cvs.horde.org/diff.php/imp/docs/CHANGES?r1=1.1178&amp;r2=1.1179&amp;ty=u
http://cvs.horde.org/diff.php/imp/js/autocomplete.js?r1=1.7&amp;r2=1.8&amp;ty=u
http://cvs.horde.org/diff.php/imp/js/src/autocomplete.js?r1=1.7&amp;r2=1.8&amp;ty=u</description> 
   <pubDate>Tue, 02 Sep 2008 21:08:58 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7074#t48677</link> 
  </item> 
   
  <item> 
   <title>Changes have been made in CVS for this ticket:

http://cvs.h</title> 
   <description>Changes have been made in CVS for this ticket:

http://cvs.horde.org/diff.php/imp/docs/CHANGES?r1=1.699.2.344&amp;r2=1.699.2.345&amp;ty=u
http://cvs.horde.org/diff.php/imp/js/autocomplete.js?r1=1.3.2.4&amp;r2=1.3.2.5&amp;ty=u
http://cvs.horde.org/diff.php/imp/js/src/autocomplete.js?r1=1.3.2.4&amp;r2=1.3.2.5&amp;ty=u</description> 
   <pubDate>Tue, 02 Sep 2008 21:12:11 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7074#t48678</link> 
  </item> 
   
  <item> 
   <title>Figured out a workaround until prototypejs is updated.  Fixe</title> 
   <description>Figured out a workaround until prototypejs is updated.  Fixed for 4.2.1.</description> 
   <pubDate>Tue, 02 Sep 2008 21:12:50 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7074#t48679</link> 
  </item> 
   
  <item> 
   <title>We&#039;ve updated to 1.6.0.3 final, so I&#039;m closing this.</title> 
   <description>We&#039;ve updated to 1.6.0.3 final, so I&#039;m closing this.</description> 
   <pubDate>Sun, 09 Nov 2008 16:16:06 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/7074#t50594</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
