Closed
Bug 252886
Opened 21 years ago
Closed 15 years ago
After Empty Trash, selected mail is still visible
Categories
(Thunderbird :: Mail Window Front End, defect)
Thunderbird
Mail Window Front End
Tracking
(Not tracked)
RESOLVED
INCOMPLETE
People
(Reporter: hariskar, Unassigned)
References
Details
(Whiteboard: closeme 2010-04-08)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040722 Firefox/0.9.1+
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7) Gecko/20040722 Firefox/0.9.1+
In nightly of 22/7 (branch, installer), I noticed this: If I select one header
in Trash and click: Empty Trash, Trash empties but the body of the message I
selected is still visible untill I click somewhere.
Reproducible: Always
Steps to Reproduce:
1.Click on Trash Folder
2.Sekect a deleted email, now Subject is blue and you can read the email
3.Right click on Trash Folder and choose Empty Trash
4.Trash is empty, but the body of the selected mail is still visible, till you
click somewhere.
Actual Results:
After Empty Trash the body of the selected mail is still visible, till you click
somewhere.
Expected Results:
No mail should be visible
Windows XP SP1
Reporter | ||
Comment 1•21 years ago
|
||
I have to make a small corection: After Empty Trash the body of the selected
mail is still visible, till you click on another folder.
Comment 2•20 years ago
|
||
This is Seamonkey bug 192870.
Severity: normal → minor
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows XP → All
Hardware: PC → All
Version: unspecified → Trunk
Updated•18 years ago
|
QA Contact: front-end
Updated•16 years ago
|
Assignee: mscott → nobody
Comment 4•15 years ago
|
||
can you reproduce this in version 3?
I can't reproduce in v3.1.
Whiteboard: closeme 2010-04-08
Comment 5•15 years ago
|
||
RESOLVED INCOMPLETE due to lack of response to last question. If you feel this change was made in error, please respond to this bug with your reasons why.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•