Closed Bug 381265 Opened 18 years ago Closed 16 years ago

Failure of the Delete button to close message window.

Categories

(Thunderbird :: Mail Window Front End, defect)

Product:
Thunderbird
Component:
Mail Window Front End
Platform:
x86
Windows XP
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 379623

People

(Reporter: rdwelch, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3 Build Identifier: 2.0.0.0 (20070326) Occasionally when I have read a message and click on the Delete button in the message window, the message window doesn't close. The button can be repeatedly clicked and appears to accept the action but the message remains displayed. I can click on the X in the upper right corner of the message window and the message window closes and the message has been deleted from the Inbox in the message list pane. This problem continues to happen with all of the messages I may display during a given session. It may or may not happen the next time I open Thunderbird. I don't know whether or not it is associated with the Tag problem or not. Before I display any messages I manually run the filters on the Inbox to display the tags. This problem did not occur in version 1.5. Reproducible: Sometimes Steps to Reproduce: 1. Still trying to find exact circumstances to reproduce 2. 3. Should have closed the message window. It appears that it did delete the message from the message list pane.
Anything in the Error Console when it happens?
Version: unspecified → 2.0
No, in fact I cleared the Error Console and I had three messages in the Inbox including yours. None of them could be deleted after manually running the filters and reading them. After failing to delete the messages using the Delete button, each message was retired using the X in the upper right corner of the message window. The message was found to be deleted in the message list pane. I immediately checked the Error Console and it was empty.
Today I again had the problem of failing to retire the message when the delete key is depressed. I checked the Error console and this time I had four entries. Three were "Expected declaration but found "*"." One was "Error in parsing value for property "font"." I don't know if these errors were indicators of the delete problrm or not. I have had the problem every day or so with no Error Console messages until this time. Perhaps they were representative of some other problem.
I experience this same condition since I downloaded the most recent update to Thunderbird. I did not have this problem before. Again, the message is deleted but the message window remains. It should, as other mail clients do, advance to the next message. If there is a setting that needs adjusting, I'm all ears.
With update to version 2.0.0.9 (from .6) this delete problem has appeared on one of our Thunderbirds. If you close Thunderbird and re-open, it seems to start to behave normally (delete button advances to next message). Cannot find a pattern to when it will not delete correctly. Once it will not delete, it seems to not work until a restart. It is happening enough to annoy the heck out of my user. I'm still looking for pattern to reproduce the behavior.
I am also running in to this issue with one of my users running 2.0.0.14 any one come across some sort of solution. I have been unable to find a way to consistently replicate the issue.
I continue to have the same problem with 2.0.0.14 as with previous iterations.
Seems to me that with such a great product, one would expect a reasonably quick solution to this kind of problem. Obviously, everyone's comments and complaints are falling on deaf ears. Outlook Express doesn't have this problem. Maybe it's time...
Do you see this problem with all extensions disabled? (thunderbird.exe -safe-mode)
Assignee: mscott → nobody
I have exactly the same problem in Ubuntu 8.10. This is the bug report I opened in launchpad: https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/325691 This seems to be a duplicate of 427712 (or the other way around)
I agree to comment #10. Feel free to reopen it if I'm wrong.
Status: UNCONFIRMED → RESOLVED
Closed: 16 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.