Closed Bug 148333 Opened 23 years ago Closed 23 years ago

does not advance to next unread mail if in another folder

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
All
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 127311

People

(Reporter: jlg33, Assigned: sspitzer)

Details

From Bugzilla Helper: User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0rc3) Gecko/20020523 BuildID: 2002052306 When viewing mail/news messages in a separate window, and pressing N to advance to next unread message, if it's in the same folder it's fine. If it's in a different folder, a dialog box pops up offering to advance to another folder. Clicking OK or Cancel have the same effect -- the smae message is display in the window; it does not advance. Reproducible: Always Steps to Reproduce: 1.Have new mail items in more than one folder 2.Open new window to view first unread mail 3.Press N 4.Click OK to advance to next message in another folder Actual Results: DIalog closes and nothing changes Expected Results: SHould display the next unread message in the new folder
Apart from experiencing bug 59638, the rest is wfm. Pressing ok moves to the next unread message. 2002053102 trunk linux
I just downloaded the nighly build: 2002053008, windows I still get the bug. There's no problem with the advancing when using the Mail view with the preview pane, but if I'm viewing a message in a *separate window* (ie. doubled clicked on message) then it won't advance to next new message if it's in another folder. I'm using IMAP for my mail; the bug occurs between newsgroups too. Jonny
I see the same here (Linux, Build 2002052421). You get asked if you want to advance to another folder, but nothing happenes.
Status: UNCONFIRMED → NEW
Ever confirmed: true
OS: Windows 98 → All
*** This bug has been marked as a duplicate of 127311 ***
Status: NEW → RESOLVED
Closed: 23 years ago
QA Contact: olgam → laurel
Resolution: --- → DUPLICATE
marking 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.