215494 - mail address entry fields fail when deleting an email address

Status: RESOLVED DUPLICATE of bug 137818

(MailNews Core :: Composition, defect)

Description

[knackaerts]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030718
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.5a) Gecko/20030718

When starting to compose a new email, I entered several email addresses of
people I wanted to send the mail to. When you then delete one of the email
entries, you cannot add a new, edit the others, etc. Note that you have to
delete not only the whole email address, but press backspace once more so that
the full entry line is removed (I mean the line that starts with To: (or Cc:,
...). The subject field is also not accessible anymore. 

Only if you first click on another field (e.g. body, etc.), or outside the
compose window, the entries are again available.

Reproducible: Always

Steps to Reproduce:
1.Compose new email
2.Add three mail addresses
3.Select one of these and press DEL, then press backspace once more to remove
this line
4.Try now to edit one of the two left, or add a new address, or add a subject

Actual Results:  
Address entry fields block, are sort of inactive. Subject line too.

Expected Results:  
Keep on working, keep fields editable (as I was used to :-) ).

Toshiba Satellite Pro 6100

Comment 1

[Mike Cowperthwaite]

Is the problem that the addresses cannot be edited, or that the cursor is not 
visible?  I see the latter, but not the former.  (1.5 Final, Win2K)

Comment 2

[Mike Cowperthwaite]

*** Bug 218425 has been marked as a duplicate of this bug. ***

Comment 3

[Mike Cowperthwaite]

*** Bug 224269 has been marked as a duplicate of this bug. ***

Comment 4

[Mike Cowperthwaite]

There is a fairly lengthy attempt at troubleshooting this problem seen at the 
second dupe, bug 224269.  I am using Windows 2000, but all three bug reports are 
with Windows XP -- this may be an XP-specific issue.

For all reporters: which theme are you using?

Comment 5

[Mike Cowperthwaite]

*** Bug 216515 has been marked as a duplicate of this bug. ***

Comment 6

[Mike Cowperthwaite]

This may be an older bug than I realized -- dupe of bug 137818?

Comment 7

[Mike Cowperthwaite]

No response from any reporters; duping.

Those who reported the bugs dupe'd to this one may wish to add their address to 
the CC list of that bug.

*** This bug has been marked as a duplicate of 137818 ***