Closed
Bug 218964
Opened 21 years ago
Closed 21 years ago
Lose focus in compose window when deleting a recipient
Categories
(MailNews Core :: Composition, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 215169
People
(Reporter: coldchrist, Assigned: sspitzer)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0; T312461; .NET CLR 1.1.4322) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.5b) Gecko/20030827 When I delete a second or subsequent address in the compose window, that addressing subwindow denies me focus until I click elsewhere and return. Reproducible: Sometimes Steps to Reproduce: 1. Click on Compose to bring up a new email window. 2. Type "a@b.c" and hit Enter. This will bring up another "To:" prompt. 3. Hit the backspace key. Actual Results: Once you do the above, the flashing cursor icon disappears. Now if you try to click on "a@b.c" in order to edit that string, the field will not accept focus. You can successfully pull down the "To:" field and change it; this will cause focus to reappear. You can also recover focus by clicking in the compose text window and then back in the addressing window, or by switching to another app and then back. This works almost every time for me, but about one time in twenty it does not reproduce; I'm unable to figure out why. Expected Results: When I clicked on the address that field should have received focus and shown me a cursor. This is a usability concern because the keystroke sequence I give is exactly what you type if you are correcting a typo you notice after having hit enter. Hence it is likely to occur relatively frequently.
Updated•21 years ago
|
Whiteboard: dupeme
Comment 1•21 years ago
|
||
Looks a bit like bug 217390.
Reporter | ||
Comment 2•21 years ago
|
||
I reproduced this on another machine running XP Pro with the identical build to the original report. I also reproduced 217390 on the XP Pro machine and I agree, the resulting behaviour is very similar. I don't know if this is relevant in the decision to mark a duplicate, but I feel that the keystroke sequence I give that causes the bug is likely to be frequently used and that makes this a little higher priority.
Comment 3•21 years ago
|
||
Oliver gets his wish. Backspace key behavior is the key to 215169 being a better match than 217390. *** This bug has been marked as a duplicate of 215169 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
Comment 4•14 years ago
|
||
Cleanup *dupeme* whiteboard flag from bugs that are marked as Resolved Duplicate!
Whiteboard: dupeme
You need to log in
before you can comment on or make changes to this bug.
Description
•