6.0.0-beta1
9/24/25

[#5711] Automatic expansion corrupts accented characters in message composition address fields
Summary Automatic expansion corrupts accented characters in message composition address fields
Queue IMP
Queue Version 4.1.4
Type Bug
State No Feedback
Priority 2. Medium
Owners
Requester bax3 (at) bigfoot (dot) com
Created 09/11/2007 (6588 days ago)
Due
Updated 10/01/2007 (6568 days ago)
Assigned 09/11/2007 (6588 days ago)
Resolved 10/01/2007 (6568 days ago)
Github Issue Link
Github Pull Request
Milestone
Patch No

History
10/01/2007 11:40:17 PM Jan Schneider State ⇒ No Feedback
 
09/18/2007 04:38:29 PM Jan Schneider Comment #4 Reply to this comment
I can't reproduce this. And given that this behavior changes when 
using a different browser, I don't really see how this could be a 
Horde bug.
09/12/2007 02:52:52 AM bax3 (at) bigfoot (dot) com Comment #3 Reply to this comment
Windows as the server or as the client?
Windows as the client does not have this problem.  The server is *NIX.



One other potential ambiguity:  the composition default charset is 
that which is set to Western (ISO-8859-1).
09/11/2007 09:53:34 AM Jan Schneider Comment #2
State ⇒ Feedback
Reply to this comment
Windows as the server or as the client?
09/11/2007 03:45:55 AM bax3 (at) bigfoot (dot) com Comment #1
Priority ⇒ 2. Medium
Type ⇒ Bug
Summary ⇒ Automatic expansion corrupts accented characters in message composition address fields
Queue ⇒ IMP
State ⇒ Unconfirmed
Reply to this comment
I have found that when entering accented characters in the address 
fields of a Horde3 IMP 4.1.4 WebMail message composition window on 
FreeBSD 6 or Mac OS X, the JavaScript automatic expansion code 
corrupts the field.  For example "Tést Usér" is changed to "Tést 
Usér".



Disabling JavaScript cures the problem but breaks other functionality.



This is using Firefox 2 on FreeBSD 6 or Mac OS X, with the Western 
(ISO-8859-1) charset.  Windows does not exhibit this bug.

Saved Queries