Closed Bug 127953 Opened 23 years ago Closed 23 years ago

When folder selected 'next unread' is disabled

Categories

(SeaMonkey :: MailNews: Message Display, defect)

x86
Windows 2000
defect
Not set
normal

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 112658

People

(Reporter: v.kazmirenko, Assigned: sspitzer)

Details

1) In 3-pane view if folder selected (e.g. pop account, news server, not group or subfolder inside it) 'next unread' action is disabled. There are no response on 'n', space bar and toolbar button disabled. 2) 't' - next unread thread does not jump across the groups. If all messages in newsgroup are already read, 't' do not go to next unread tread in next unread newsgroup, only 'n' and spacebar work.
QA Contact: esther → laurel
Both conditions are duplicates of existing bugs: 1. see bug 112658 (and more recent problem bug 127144) 2. see bug 66466 When reporting bugs, try to report each issue in a separate bug. *** This bug has been marked as a duplicate of 112658 ***
Status: UNCONFIRMED → RESOLVED
Closed: 23 years ago
Resolution: --- → DUPLICATE
marking verified as duplicate
Status: RESOLVED → VERIFIED
laurel, none of the bugs you quote appear to refer to accounts, victor appears to want next unread when account central is open.
Sorry for poor English. I do not fully understand what is 'account central'. I'll try to explain in a words that I understand. There are accounts tree in a leftmost pane. Root branches are account names, e.g. mypop, local folders, mynews and so on. That root branches have a subfolders, Inbox, drafts etc for mail accounts and newsgroups for news servers. So, if folder or newsgroup marked it works fine. But if root branch is selected - mail or news - 'next' appears disabled. As to relation with quoted bug I'm not sure are they really of the same nature or not. Trust developers.
Also see bug 65733 for the server/account central case.
Oh yeah... one of mine... /me looks somewhat sheepish :-)
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.