Closed
Bug 283650
Opened 20 years ago
Closed 19 years ago
Compose data entry not possible after switching to compose window from 3pane
Categories
(Thunderbird :: Message Compose Window, defect)
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: tatlar, Assigned: mscott)
Details
User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X; en) AppleWebKit/125.5.6 (KHTML, like Gecko) Safari/125.12 Build Identifier: version 1.0 (20041206) When I open TB it all works fine until I compose a new message (also applies to replies). When the new message composer window pops up, if I click back to the main inbox viewer and then back to the composer window I cannot enter anything in the fields (to, cc, subj, message etc). If I click on another application (not TB) and then re-click back on the message window I CAN fill out the fields. However, if I click back into the main TB view window at any time and then click back into the TB message being composed I again cannot edit. The cursor is there but when I press any key it does not come up on the screen. Reproducible: Always Steps to Reproduce: 1. Open TB 2. Hit the 'write' button - a new compose message window opens 3. Click back to the main inbox viewer (unfocus message compose window) 4. Click back into the compose message window (refocus message compose window) Actual Results: Cannot edit any of the fields in the compose message window Expected Results: I should be able to add information to all the fields. Does not crash the application. Just a glitch.
Comment 1•20 years ago
|
||
Frankie, can you look at this one?
Summary: can enter the information ok when I try and compose new message I cannot enter any addresses or text if I have switched back to the main view window inbetween and then back again to the message composer. If I select any another application and then refoc… → Compose data entry not possible after switching to compose window from 3pane
WFM Tbird 1.0 OSX 10.3.8, no problem clicking back and forth between compose and mailbox.
Comment 3•19 years ago
|
||
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/
Comment 4•19 years ago
|
||
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.
Description
•