The behaviour of the Aucomplete is inconstistent:the non-ascii name could be found randomly but most of the cases it is not (if you explicitely type a non-ascii chars it would not be found, it would autocomplete like " má@netscape.com". When the non-ascii chars is on a first position (starting the name) it is never recognized. Steps to reproduce: -eneter several new AB cards with non-ascii chars in it; -send messages using those cards entries for them to get into Collected Addresses; -close and restart AB; -open New message, type M+"Alt+0xxx" (the beginning of the non-ascii name) and see the result //non-ascii name is not found, instead it autocompletes like M+"Alt+0xxx"@netscape.com
Assignee: nhotta → ducarroz
Summary: AutoComplete against Collected Addresses is not working for 8bit chars → AutoComplete against Collected Addresses is not working for 8bit chars
Reassign to ducarroz.
Status: NEW → ASSIGNED
Target Milestone: M12
Let's not spend any more time than necessary on the temporary autocomplete code. JF will be writing the real autocomplete code for B2.
Mass moving to M16 to get these off the M15 radar. Please let me know if this is really an M15 stopper.
Target Milestone: M15 → M16
This problem is gone with the new autocomplete
Status: ASSIGNED → RESOLVED
Last Resolved: 19 years ago
Resolution: --- → FIXED
verified as fixed in 2000-05-02 build
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.