Closed
Bug 184887
Opened 22 years ago
Closed 21 years ago
Changing email accounts when sending mail affects focus
Categories
(MailNews Core :: Composition, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: cooperg, Assigned: bugzilla)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021123 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.3a) Gecko/20021123 At work I have both my work and personal email addresses set up in MozMail. My work account has a signature, the other does not. If I start a mail message then change what account I'm sending from the blinking cursor still stays in the composition area but if I type text nothing happens. I have to actually click the mouse in the composition area in order to begin typing again. Reproducible: Always Steps to Reproduce: 1. compose a new mail message, type some stuff in to the composition area 2. change which account you're sending FROM (by mouse operation) 3. note that the cursor is still holding your place in the composition area 4. attempt to continue your mail message (by typing). Expected Results: Expected result would have been that it let me continue typing. The easy fix would be to remove the blinking cursor from the composition area, implying that the focus is now on the FROM area but I would rather be able to continue typing my message. :/
Comment 1•21 years ago
|
||
Reporter (cooperg): The symptom you describe still exists in 1.3 Final (probably in 1.3.1, as well) but the behavior has changed in 1.4 -- as of RC2, at the latest, selecting a new identity in the From: moves the focus to a new To: field in the address block, with the cursor blinking there and keystrokes appearing there. Maybe not the ideal solution, but at least the confusion is gone.
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → WORKSFORME
Updated•20 years ago
|
Product: MailNews → Core
Updated•16 years ago
|
Product: Core → MailNews Core
You need to log in
before you can comment on or make changes to this bug.
Description
•