Closed Bug 1007354 Opened 10 years ago Closed 10 years ago

When selecting an email recipient from the address book, if the "Display Name" contains a comma, a duplicate "To" entry is created with the same email address and the portion of the "Display Name" that follows the comma.

Categories

(SeaMonkey :: MailNews: Composition, defect)

Product:
SeaMonkey
Component:
MailNews: Composition
Version:
SeaMonkey 2.26 Branch
Platform:
x86
macOS
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 966053

People

(Reporter: jkviscosi, Unassigned)

Details

User Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.9; rv:29.0) Gecko/20100101 Firefox/29.0 SeaMonkey/2.26 (Beta/Release)
Build ID: 20140428215742

Steps to reproduce:

Compose, reply to, or forward an email.  Select a recipient from the address book whose display name contains a comma.


Actual results:

The recipient is inserted onto the current "To" line, and the same email address is inserted onto the following "To" line, associated with just that portion of the display name to the right of the comma.  If focus is returned to the "To" line that contains the full display name and then focus is changed, the duplicate email address occurs again, except this time all that is left in the original "To" field is the portion of the display name to the left of the comma, while the portion to the right of the comma (including the email address) is inserted onto another new "To" line.


Expected results:

The full display name and email should be inserted into the current "To" field.  None of the other effects described should occur.
> Select a recipient from the address book whose display name contains a comma.
IS the name surrounded by double quotes? e.g.
"Smith, Fred" <fsmith@example.org>
In the address book?  No, I have never used double-quotes in any display names in the address book, and they worked as expected until version 2.26.  I just tested surrounding one of the offending display names in the address book with double-quotes and the undesired behavior stopped, so I will do that as a workaround.  Thanks for the tip!
I'm confirming this report is valid. It was starting to drive me batty so I'm glad there's a workaround identified.
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.