Closed Bug 288241 Opened 20 years ago Closed 19 years ago

E-mail address duplicated when composing message with nicknames

Categories

(Thunderbird :: Message Compose Window, defect)

x86
Windows XP
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED EXPIRED

People

(Reporter: RMadisonWI, Assigned: mscott)

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2
Build Identifier: version 1.0.2 (20050317)

If I am sending a message to someone using a nickname, and accidentally hit
extra punctuation, then the recipient's name will appear twice in the "to"
fields (one on each of two lines).  This is pretty consistent, though through
trying different things, I haven't been able to reproduce it 100% of the time. 
I'd say 50% or more, though, it happens.

Reproducible: Always

Steps to Reproduce:
Let's say I have someone in my address book with the initials ABC, so I decide
to give him the nickname "abc" to make it easier to compose a message to him. 
Let's also say there's someone nicknamed "def," and I want to send both of them
a message.

1.  Open new message window
2.  Type "abc,," (with both commas) in the "To" field.
3.  Delete (i.e. with backspace) the two commas, then type another comma, and
then type def
4.  Press "Tab" to jump to the subject field

Actual Results:  
When I do this (often caused by me typing too fast, and I screw up the
punctuation between the two e-mail recipients, so I delete the bad punctuation
and try again), I'll get the first recipient's address listed twice.  I.e.

To:  abc@email.com
To:  abc@email.com
To:  def@email.com

Expected Results:  
What should happen is that the first recipient only has his/her e-mail address
listed once.  I.e.

To: abc@email.com
To: def@email.com
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.