Closed Bug 1026394 Opened 10 years ago Closed 10 years ago
TB 31 - On new message compose windows, contacts autocomplete isn't working properly
TB 31 beta 1 LDIF contact example, extracted from my addressbook: dn: cn=Tester Lastname, Tester Test,firstname.lastname@example.org objectclass: top objectclass: person objectclass: organizationalPerson objectclass: inetOrgPerson objectclass: mozillaAbPersonAlpha givenName: Tester Test sn: Tester Lastname cn: Tester Lastname, Tester Test mail: email@example.com modifytimestamp: 0 Reproduce: 1. Compose new message 2. Enter "tester" in first To: field 3. You will get autocomplete suggestion for "tester Lastname, Tester Test <firstname.lastname@example.org>" 4. Press ENTER Expected: Contact will be in first To: field Result: Contact was splitted into 2 contacts, first one being contact last name, and second one his first name + email address. If I try to send email now, I get error saying: "Invalid RFC821 mailbox specification.. Check mail receiver "tester Lastname" and try again." Picture attached.
I forget who was working on the autocomplete issues, but this sounds similar to the one we had for normal autocomplete.
Absolutely this is a serious issue and needs swift resolution. (I'm seeing something like this myself) But blocker in bugzilla means blocks developer work, so is a bit too strong for this issue.
Severity: blocker → major
Status: UNCONFIRMED → RESOLVED
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.