Closed Bug 216341 Opened 22 years ago Closed 21 years ago

Select "Next" message not selecting with 1 message

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 201392

People

(Reporter: frank.holden, Assigned: sspitzer)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4b) Gecko/20030507 When a new message arrives, only one, that is NOT filtered to the trash, it can not be selected with the next button within following folders even if the inbox is highlighted. It works fine as long as you have 2 or more messages within any folder but trash... Example: folder names of SAVE, HOLD, BUSINESS and LINUX will appear below the TRASH folder. If a message goes into any one of those folders thru filtering and only one message comes in, next will not select it. If a message goes into 2 of those 4 folders then it will select the next message, but never the last one. Reproducible: Always Steps to Reproduce: 1.Get one new email message in any other folder besides inbox 2.Click on inbox if you wish (preferred) 3.Click on NEXT button... Actual Results: Did not go to the next unread email even though the folder was highlighted as a new message had arived there... It makes no difference what folder you are in above the one with the new email in it. Expected Results: Go to the next/last available message in the next folder or the last available message left in another folder.
yeah, i can confirm on Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4) Gecko/20030624 and im certain this bug was introduced recently, probably 1.4
Duplicate is fixed, in 1.5 and also will be in 1.4.2 whenever that's released. *** This bug has been marked as a duplicate of 201392 ***
Status: UNCONFIRMED → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.