Recipient autocomplete angle brackets characters (doe >> John Doe <john@asdf.com>) remain in recipient field and get sent with message header (when clicking send without manually confirming autocomplete)

NEW
Assigned to

Status

8 years ago
4 years ago

People

(Reporter: firstpeterfourten, Assigned: mkmelin)

Tracking

({privacy})

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

8 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101203 Firefox/3.6.13
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7

When typing in an address, the autocomplete mechanism adds a string of the form " >> Contact name <username@example.com>" in the "To" (CC, etc.) field.  This string remains there when the message is sent, if there are no other user events that switch the focus away and cause the extra string to be removed. 

Reproducible: Always

Steps to Reproduce:
1. Open a new e-mail message in the Compose window.
2. Add in a subject and body;  the "blank subject" dummy-check would be enough to cause non-observation of this bug.
3. Just before you're ready to send the message, add a recipient.  It doesn't matter if this is the first or a later recipient, only that they're already in your address book/list of e-mail addresses. 
4. For example, we'll add "Example Recipient <firstfewletters@example.com>."  Do this by typing in "first".
5. Mozilla will change the string to read "first >> Example Recipient <firstfewletters@example.com>"
6. Click Send, or use the keyboard shortcut to send. 
Actual Results:  
The message is actually sent, to "first >> Example Recipient <firstfewletters@example.com>".
While this particular example would still result in mail delivery, that's less clear if I had continued typing and the mail was sent to "firstfewletters@example.com >> Example Recipient <firstfewletters@example.com>" as happened with a recent e-mail that I sent.  

Expected Results:  
The text should disappear, the same behavior as if I'd clicked away (e. g. in the Compose Body field) instead of clicked Send.  If I had typed in a full e-mail address that should be fine and it should be sent to just "firstfewletters@example.com" instead of the full string.  If I had not entered in a full e-mail address (e. g. "firstfew") it should report an Invalid Recipient Address.  Automatically choosing the first result (as done when a user clicks away to edit the message body) may not be a good idea because the sender has no chance to review this decision and see if that's actually who they intend to send the message to.
this happens. nothing bad happens right? unsure if it's a duplicate.

WBT, shorter STR descriptions would be helpful - you put up a lot of words to read.  TIA
Severity: normal → minor
Status: UNCONFIRMED → NEW
Component: Address Book → Message Compose Window
Ever confirmed: true
QA Contact: address-book → message-compose
Whiteboard: [dupeme?]
Still happens as described for TB17 on WinXP, this should be linked up to depend that other bug that we are too agressive in autocompleting the first match without user action.
Summary: Autocomplete characters remain in line when message is sent → Recipient autocomplete angle brackets characters (jo >> John Doe <john@asdf.com>) remain in recipient field and get sent with message header (when clicking send without manually defocusing address widget)
Whiteboard: [dupeme?] → [dupeme?][dependme]
This happens now even when you're starting to compose a new email -- e.g. type a query into the "To" box, watch Autocomplete complete it, and then hit "tab" a few times to switch to the Subject field. Your "To" field will be left in a busted-looking state, with the search query and the ">>" before the contact.

I'm pretty sure this didn't used to happen with those STR. (At least, these STR are my muscle memory for how to compose an email, and I don't recall it being broken until relatively recently.)
The new bug is 1003856, which should be already fixed, last result on Wayne's search. Magnus clipped the summary to not contain >>.
See Also: → bug 1003856, bug 348844
(In reply to Wayne Mery (:wsmwk) from comment #4)
> I am also seeing this behavior when using nightly. 

Wayne's comment made me test this some more, and indeed, it still fails for important scenarios e.g. when you tab out of recipient field to accept the suggestion, or when TB composition loses focus while the suggestion is active (bug 1009469). Thanks Wayne, helpful comment. :)

Please keep testing this and report anything odd...
(Assignee)

Comment 7

5 years ago
This is still an issue after bug 1009469, though a bit of an edge case.
Assignee: nobody → mkmelin+mozilla
OS: Windows 7 → All
Hardware: x86 → All
Whiteboard: [dupeme?][dependme]
(In reply to Magnus Melin from comment #7)
> This is still an issue after bug 1009469, though a bit of an edge case.

Less of an edge case might be this variant:
[cursor right] to select first result [searchwords >> matchingContact <email>], then clicking into next recipient input box will also leave the "searchwords >>" part sticking around instead of normalizing the result by removing the searchword and >>, as we correctly do on subsequent results when selected with cursor right.
Still seen on TB 31.5.0

Edge case or not, this violates user's privacy because the message actually gets sent out, but potentially to a different, valid email address, e.g.:

"doe >> john.doe"@asdf.com

User will also wrongly believe the msg has been sent successfully, until the error mail from the smpt server arrives.
Severity: minor → normal
Keywords: privacy
Summary: Recipient autocomplete angle brackets characters (jo >> John Doe <john@asdf.com>) remain in recipient field and get sent with message header (when clicking send without manually defocusing address widget) → Recipient autocomplete angle brackets characters (doe >> John Doe <john@asdf.com>) remain in recipient field and get sent with message header (when clicking send without manually confirming autocomplete)
You need to log in before you can comment on or make changes to this bug.