Closed
Bug 252981
Opened 21 years ago
Closed 19 years ago
With preview pane closed, deleting or moving an open message marks next message as read
Categories
(SeaMonkey :: MailNews: Message Display, enhancement)
SeaMonkey
MailNews: Message Display
Tracking
(Not tracked)
RESOLVED
EXPIRED
People
(Reporter: ydavid, Unassigned)
References
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040608
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7) Gecko/20040608
Preview pane is closed and a message is open in the background. Deleting or
moving the open message in the mailbox window marks the next message as read and
opens it in the background message window while focus remains on the mailbox window.
Reproducible: Always
Steps to Reproduce:
1. Make sure preview pane closed
2. Double click on a message in a mailbox window. Focus changes to message window.
3. Return to mailbox window.
4. Delete message in mailbox window or move it to another mailbox.
Actual Results:
Next message changes to marked as read and opens in the background in the
message window.
Expected Results:
Next message should not change to marked as read and should not open in the
background.
If the preview pane were open, the next message should open there and change to
marked as read, but this should not occur in the background where one might not
notice.
I suspect this might be related to bug 75866 though it's not quite the same thing.
Netscape 4.7x did not behave this way though it did exhibit the behavior
discussed in bug 75866, which is why I always keep the preview pane closed.
Comment 1•20 years ago
|
||
*** Bug 269256 has been marked as a duplicate of this bug. ***
Comment 2•20 years ago
|
||
(In reply to comment #0)
> If the preview pane were open, the next message should open there and change
> to marked as read, but this should not occur in the background where one might
> not notice.
Bug 232411 asks for this same behavior even in the preview pane.
Severity: normal → enhancement
OS: Windows 2000 → All
Hardware: PC → All
Updated•20 years ago
|
Product: Browser → Seamonkey
Updated•20 years ago
|
Assignee: sspitzer → mail
Comment 3•19 years ago
|
||
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/
Comment 4•19 years ago
|
||
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
Closed: 19 years ago
Resolution: --- → EXPIRED
You need to log in
before you can comment on or make changes to this bug.
Description
•