<?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>No keyboard nav on expanded addresses in IE 7</title> 
  <pubDate>Fri, 10 Apr 2026 00:23:11 +0000</pubDate> 
  <link>https://bugs.horde.org/ticket/6656</link> 
  <atom:link rel="self" type="application/rss+xml" title="No keyboard nav on expanded addresses in IE 7" href="https://bugs.horde.org/ticket/6656/rss" /> 
  <description>No keyboard nav on expanded addresses in IE 7</description> 
 
   
   
  <item> 
   <title>In IE7, neither tab or enter select the first expanded addre</title> 
   <description>In IE7, neither tab or enter select the first expanded address in the compose window, and the arrow keys don&#039;t navigate through the list.</description> 
   <pubDate>Sun, 27 Apr 2008 22:04:12 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6656#t44963</link> 
  </item> 
   
  <item> 
   <title>Looks like this:

http://dev.rubyonrails.org/ticket/10126</title> 
   <description>Looks like this:

http://dev.rubyonrails.org/ticket/10126</description> 
   <pubDate>Fri, 02 May 2008 17:51:06 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6656#t45133</link> 
  </item> 
   
  <item> 
   <title>Sheesh. So we&#039;re waiting on what, 3 different prototype/scri</title> 
   <description>Sheesh. So we&#039;re waiting on what, 3 different prototype/scriptaculous bugfixes?</description> 
   <pubDate>Fri, 02 May 2008 17:59:43 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6656#t45142</link> 
  </item> 
   
  <item> 
   <title>Going against my previous statements, I think we should prob</title> 
   <description>Going against my previous statements, I think we should probably make the necessary changes ourselves (especially with that rather nasty IE offsetParent issue in the other ticket) because it seems that we are not going to get resolution of this in the upstream distributions in the next few weeks.</description> 
   <pubDate>Fri, 02 May 2008 18:04:21 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6656#t45144</link> 
  </item> 
   
  <item> 
   <title>Okay by me.</title> 
   <description>Okay by me.</description> 
   <pubDate>Fri, 02 May 2008 18:29:28 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6656#t45147</link> 
  </item> 
   
  <item> 
   <title>Here&#039;s my proposed patch to controls.js for this.</title> 
   <description>Here&#039;s my proposed patch to controls.js for this.</description> 
   <pubDate>Fri, 02 May 2008 20:27:17 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6656#t45149</link> 
  </item> 
   
  <item> 
   <title>Applied the patch.  Keeping bug open to track when we don&#039;t </title> 
   <description>Applied the patch.  Keeping bug open to track when we don&#039;t need to apply patch to upstream source.</description> 
   <pubDate>Mon, 05 May 2008 19:17:54 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6656#t45174</link> 
  </item> 
   
  <item> 
   <title>Stalling like the other bugs like this.</title> 
   <description>Stalling like the other bugs like this.</description> 
   <pubDate>Mon, 19 May 2008 00:24:11 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6656#t45359</link> 
  </item> 
   
  <item> 
   <title>I believe this has been fixed upstream.  At a minimum I have</title> 
   <description>I believe this has been fixed upstream.  At a minimum I haven&#039;t applied to newer versions of prototype and it works fine with the latest releases.</description> 
   <pubDate>Thu, 28 May 2009 16:32:21 +0000</pubDate> 
   <link>https://bugs.horde.org/ticket/6656#t54334</link> 
  </item> 
   
   
 
 </channel> 
</rss> 
