Closed Bug 153837 Opened 22 years ago Closed 22 years ago

When message is deleted next message is opened in its window.

Categories

(SeaMonkey :: MailNews: Message Display, enhancement)

x86
Windows 2000
enhancement
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 80574

People

(Reporter: arnova, Assigned: sspitzer)

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.1a) Gecko/20020611 BuildID: 2002061104 When a seperate Window is used to read email instead of the small window on the bottom of the screen this problem occurs: When a message is opened in a seperate Window and that message is deleted from the inbox (by selecting it and pressing delete), the next message is automatically opened in the window which previously showed the deleted message. Reproducible: Sometimes Steps to Reproduce: 1.Config mail to show messages a seperate Window 2.Open a message from the inbox 3.Now it is shown in a seperate Window 4.Delete the message from your inbox 5.Now the message Window shows the next email in the inbox (now highlighted) Actual Results: The seperate message window shows the next email in the inbox (message highlighted after removal of the original message) Expected Results: The message window should be closed. This also causes previously "unread" messages to become "read" (not bold anymore) which isn't really handy.
Severity: normal → enhancement
Status: UNCONFIRMED → NEW
Ever confirmed: true
QA Contact: olgam → laurel
Not everyone agrees on the delete behavior in the standalone window. There is an existing request for a pref to have the window close on delete -- see bug 80574. There have also been bugs in recent past to have this current behavior, to go to next message -- a few bugs on this, one is 132009. *** This bug has been marked as a duplicate of 80574 ***
Status: NEW → RESOLVED
Closed: 22 years ago
Resolution: --- → DUPLICATE
verified as a duplicate
Status: RESOLVED → VERIFIED
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.