If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

"Next Unread Message" no longer works

RESOLVED WORKSFORME

Status

SeaMonkey
MailNews: Message Display
RESOLVED WORKSFORME
14 years ago
13 years ago

People

(Reporter: K. Richard Pixley, Assigned: (not reading, please use seth@sspitzer.org instead))

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6) Gecko/20040113
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.6) Gecko/20040113

As of sometime in the 1.6 development, "next unread message" stopped finding
unread messages in collapsed folders.  Now I must dig around in my folder tree
manually to find the unread message.

Reproducible: Always

Steps to Reproduce:
1. create an account
2. create a folder "A"
3. create a folder "B" in folder "A"
4. put an unread message in folder "B"
5. collapse folder A, (ie, hide contents)
6. position on a message in an earlier folder, say, your INBOX.
7. "next unread message"

Actual Results:  
Nothing at all.

Expected Results:  
Mozilla should expand the collapsed folder, position on folder B, and display
the unread message.

Previous versions did not have this flaw.
Product: Browser → Seamonkey

Comment 1

13 years ago
Are you still seeing this behavior? If so, which window mode are you using?
I.e., do you read you mail in the 3-pane window, or in a separate window?
(Reporter)

Comment 2

13 years ago
I've just retested mozilla-1.8a5 on windows, linux, and macos.  All three appear
to be working correctly now.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago
Resolution: --- → FIXED

Comment 3

13 years ago
No specific bug / patch identified as the fix.

-> WORKSFORME.
Status: RESOLVED → UNCONFIRMED
Resolution: FIXED → ---

Updated

13 years ago
Status: UNCONFIRMED → RESOLVED
Last Resolved: 13 years ago13 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.