User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322) Build Identifier: version 0.9 This is posted in the mozillazine Thunderbird bugs forum: http://forums.mozillazine.org/viewtopic.php?t=166108 Hi THere... I'm experiencing what I would call a bug. When I click compose, and then say change my mind not wanting to send the mail, the compost window will not close at all. I get the "do you want to save a draft" message, I choose no, and the compose window freaks out. The top header stays, but the rest is sort of transparent, and the window will not close unless I close out Thunderbird all together. Using Thunderbird 0.9 on XP SP2. Thanks! Yep, I can confirm this bug, it happens to me too. I've also seen it happen when I actually compose a message, send it and after a while there's this shadow window hiding behind my main TB window, I call it shadow because it only has the borders and title bar but everything inside is transparent. The window cannot be closed either, the only way to make it go away is to close TB. NOTE: I am using multiDesk (a multi dekstop manager), so it may be related, but I don't see similar behavior with other applications (and I use lots of apps), only Thunderbird seems to leave these shadow windows behind. Reproducible: Sometimes Steps to Reproduce: 1. Start composing a new message 2. Cancel message composition Actual Results: A shadow window remains that cannot be closed. Expected Results: Compose window should go away. NOTE: I am using multiDesk (a multi dekstop manager), so it may be related, but I don't see similar behavior with other applications (and I use lots of apps), only Thunderbird seems to leave these shadow windows behind.
It still happens in the 1.0 build 20041205 Is there anything special about closing the window to really make it go away?
Created attachment 168969 [details] Screenshot of the problem Screenshot of the problem as of Thunderbird 1.0 official release build.
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/
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
Last Resolved: 13 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.