Closed
Bug 288867
Opened 20 years ago
Closed 19 years ago
cursor keys don't work in new mail window after I used send to mail recipient menu in windows (file) explorer
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
RESOLVED
WORKSFORME
People
(Reporter: atanczos, Assigned: mscott)
References
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; hu-HU; rv:1.7.6) Gecko/20050317 Firefox/1.0.2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; hu-HU; rv:1.7.6) Gecko/20050317 Firefox/1.0.2 Cursor keys don't work in new mail window after I used send to mail recipient menu in windows (file) explorer to create a new mail with attachment. This happens if the Thunderbird is not started. Besides the program slows down the computer (only in this case). Reproducible: Always Steps to Reproduce: 0. close thunderbird 1. start windows explorer 2. select a file 3. right click to open context menu 4. select send to -> mail recepient Actual Results: 1. the cursor keys don't work in new mail window 2. the computer slows down Expected Results: the cursor keys should work
| Reporter | ||
Updated•20 years ago
|
Version: unspecified → 1.0
Comment 1•19 years ago
|
||
I can see this behaviour also with Version 1.0.5 (20050709), but it happens not always. Most of the times I can force the error by typing part of the recipients name and then selecting one name with the cursor. When clicking then into the subject field and try to move the cursor in the standard subject text, it doesn't work. Very seldom I cannot move the cursor in the message body. If Thunderbird is already open, this error doesn't occur.
Comment 2•19 years ago
|
||
One additional info: if I enable JavaScript at thunderbird, the error doesn't occur.
Comment 3•19 years ago
|
||
I can reproduce this with TB 1.0, but it appears to be fixed in TB 1.5 -- possibly by the patch at bug 303976.
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
Comment 4•19 years ago
|
||
*** Bug 312152 has been marked as a duplicate of this bug. ***
You need to log in
before you can comment on or make changes to this bug.
Description
•