When there are no more unread messages in the current folder, MailNews correctly asks if you want to read the next unread message in the next folder. However, if no other folder contains any unread messages, the Next button remains enabled but clicking on it does nothing. Expected behavior should be either: 1) Next button is disabled OR 2) Next button is enabled but clicking on it displays a dialog box saying "There are no more unread messages in any folder."

1) sounds reasonable. I cannot find a dupe. pi

Or both. Like it displays a dialog box saying "There are not more unread messages in any folder" and then disables it?

*** This bug has been marked as a duplicate of 60153 ***

No, this is not a dupe. Unlike Bug 60153, this one understands that the Next should go to the next folder in case a folder is empty. However, when ALL folders are already exhausted and there are no more unread messages in ANY folder, then it makes sense to gray out the Next button. It's confusing to keep on clicking the Next button thinking I have unread messages in another folder, but getting no results.

MASS-CHANGE: This bug report is registered in the SeaMonkey product, but has been without a comment since the inception of the SeaMonkey project. This means that it was logged against the old Mozilla suite and we cannot determine that it's still valid for the current SeaMonkey suite. Because of this, we are setting it to an UNCONFIRMED state. If you can confirm that this report still applies to current SeaMonkey 2.x nightly builds, please set it back to the NEW state along with a comment on how you reproduced it on what Build ID, or if it's an enhancement request, why it's still worth implementing and in what way. If you can confirm that the report doesn't apply to current SeaMonkey 2.x nightly builds, please set it to the appropriate RESOLVED state (WORKSFORME, INVALID, WONTFIX, or similar). If no action happens within the next few months, we move this bug report to an EXPIRED state. Query tag for this change: mass-UNCONFIRM-20090614

MASS-CHANGE: This bug report is registered in the SeaMonkey product, but still has no comment since the inception of the SeaMonkey project 5 years ago. Because of this, we're resolving the bug as EXPIRED. If you still can reproduce the bug on SeaMonkey 2 or otherwise think it's still valid, please REOPEN it and if it is a platform or toolkit issue, move it to the according component. Query tag for this change: EXPIRED-20100420