Closed Bug 225447 Opened 21 years ago Closed 19 years ago

Deleting new email with attachments fails to go to next email in Inbox

Categories

(Thunderbird :: Mail Window Front End, defect)

Other
Other
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: deggs, Assigned: mscott)

References

()

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-GB; rv:1.0.1) Gecko/20020823 Netscape/7.0
Build Identifier: 

Scenario : Inbox has multipul emails, some with attachments.

Action : You start with the first email (no attachment), and read it and then
delete it.  Thunderbird then goes to the next email in the Inbox.  Cool. 
However, if the email has an attachment and you delete it, Thunderbird goes to
the next email in the Inbox, but does not display the emails contents on the
bottom half of the screen.

Reproducible: Always

Steps to Reproduce:
1. Send 5 emails to an account, the forth having an attachment (pdf or something)
2. Log into the account and click on the first email. Email contents are shown
in the bottom half of the screen.
3. Delete the email and thunderbird will move to email #2 and display the contents.
4. Delete the second email and thunderbird will move to email #3 and display the
contents.
5. Delete the third email and thunderbird will move to #4 and display the contents.
6. Delete the forth email and thunderbird will move to email #5, but will not
show contents within the bottom half of the screen.
Actual Results:  
Any email with an attachment, when deleted does not show the following email as
it does if the email being deleted does not have an attachment.

Expected Results:  
Trying this from Windows XP and this seems fine, so must be something with the
compile on to Solaris platform.

I am running Solaris 8 X86 and thunderbird 0.3 contrib.
Is this bug still a problem with current TB builds?  If not, please mark it:
  Resolved | WorksForMe
Severity: major → normal
No response from reporter  =>  WFM
Status: NEW → RESOLVED
Closed: 19 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.