User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:18.104.22.168) Gecko/20091102 Firefox/3.5.5 Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:22.214.171.124) Gecko/20091204 Thunderbird/3.0 When switching from View All to View Unread oftentimes both entries are selected. This is very irritating. Wenn I come from View All, I expect only View All to be selected. This bug was in all nightlies and made it to TB3 Final. (See image for better understanding.) Reproducible: Sometimes Steps to Reproduce: I encounter this behaviour several times a day, but not always.
Error console is empty not clear STR but not really difficult to get into.
Status: UNCONFIRMED → NEW
Component: Mail Window Front End → Folder and Message Lists
Ever confirmed: true
QA Contact: front-end → folders-message-lists
sounds like this doesn't affect the view itself, so minor. Mac only?
Severity: normal → minor
(In reply to comment #3) > sounds like this doesn't affect the view itself, so minor. Mac only? Indeed.
Summary: Both "unread" and "all" in View menu are selected → Both "unread" and "all" in View menu are selected [Mac]
blocking-thunderbird3.1: --- → -
Is this still seen in 3.1 or alpha 3.3? Bwinton, I'd think this is core bug, not thunderbird, no?
Could be… I've checked the code, and I don't see anything particularly strange that we're doing to cause this, so yeah, I would believe this might be a core bug. Thanks, Blake.
Created attachment 631073 [details] View_All_Unread_screenshot.png I see this bug every day. It's pretty annoying. I'm currently using Thunderbird 13.0 on Mac OS X 10.7.4, but I have seen this problem for along time. The STR are intermittent but easily repeatable. STR: 1. Select an IMAP folder in Thunderbird's Folder Pane 2. Open View toolbar menu and check the Unread menu item 3. Select a different IMAP folder 4. Open View toolbar menu and check the All menu item 5. Switch back to the IMAP folder from step 1 6. Open View toolbar menu AR: Both All and Unread menu items are checked. See the attached screenshot.
You need to log in before you can comment on or make changes to this bug.