[Tickets #6710] "Switch to ... composition" broken in IE6/7

bugs at horde.org bugs at horde.org
Thu May 15 16:16:58 UTC 2008


DO NOT REPLY TO THIS MESSAGE. THIS EMAIL ADDRESS IS NOT MONITORED.

Ticket URL: http://bugs.horde.org/ticket/6710
-----------------------------------------------------------------------
 Ticket             | 6710
 Created By         | liamr at umich.edu
 Summary            | "Switch to ... composition" broken in IE6/7
 Queue              | IMP
 Version            | FRAMEWORK_3
 Type               | Bug
 State              | Unconfirmed
 Priority           | 1. Low
 Milestone          |
 Patch              |
 Owners             |
-----------------------------------------------------------------------


liamr at umich.edu (2008-05-15 12:16) wrote:

We're using IMP 4.2RC4 w/ templates/compose/compose.html,
js/src/compose.js, js/src/SpellChecker.js from FRAMEWORK_3 (and rebuilt the
js sources with the yuicompressor).

What we're finding is that users can use their default editor, but if they
choose "Switch to (HTML | plain text) composition", the browser spins and
spins and spins.  The transfer log shows a bunch of this..

141.213.xxx.xxx - - [15/May/2008:12:11:32 -0400] "POST
/horde/imp/compose.php?uniq=7cgd6vr0jv4s HTTP/1.1" 200 5652
"https://test-mail.www.umich.edu/horde/imp/compose.php?%2Fhorde%2Fimp%2Fcompose.php&mailbox=INBOX&uniq=1210867877463"
"Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1)"
141.213.xxx.xxx - - [15/May/2008:12:11:32 -0400] "POST
/horde/imp/compose.php?uniq=7cgd6vr0jv4s HTTP/1.1" 200 5652
"https://test-mail.www.umich.edu/horde/imp/compose.php?%2Fhorde%2Fimp%2Fcompose.php&mailbox=INBOX&uniq=1210867877463"
"Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1)"
141.213.xxx.xxx - - [15/May/2008:12:11:33 -0400] "POST
/horde/imp/compose.php?uniq=7cgd6vr0jv4s HTTP/1.1" 200 5651
"https://test-mail.www.umich.edu/horde/imp/compose.php?%2Fhorde%2Fimp%2Fcompose.php&mailbox=INBOX&uniq=1210867877463"
"Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 5.1)"

After mucking around with some stuff, it seems specific to js/compose.js




More information about the bugs mailing list