Closed Bug 582960 Opened 14 years ago Closed 12 years ago

When new rss messages arrive into subfolder, subfolder's name doesn't become bold.

Categories

(Thunderbird :: Folder and Message Lists, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

RESOLVED WORKSFORME

People

(Reporter: atremba, Unassigned)

References

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; ru; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 Build Identifier: 3.1.1 I have few folders under News (RSS) account. There is a global timer set to check messages (by RSS feeds) every 99 minutes (exact time seems to be not matter). Sometimes when Thunderbird checks and recieve messages into these folders, a folder with new messages doesn't change its fontface to bold blue. It should _automatically_ become blue bold and have the number of unread messages. When this "visually without new messages" folder selected, I can see new messages in message list, and folder name instantly become bold and have number of unread messages! Meanwhile some folders have normal behaviour: folder name become bold blue and a number of new messages in '()' brackets. Rarely another modification of the bug happens: folder name become bold blue, but no number of new messages displayed (nor number, nor brackets). When this folder selected, number appears. Reproducible: Couldn't Reproduce Steps to Reproduce: 1. Create few RSS feeds. 2. Set up automatic update. 3. Periodically make all messages in a folder being read. 4. Often happen on a YouTube rss feed. Actual Results: Look at a folder - visually it hasn't change fontface, but being selected, you'll see new messages in it. Folder name alse become in bold face and number of unread messages appears. Russian version. Some rss feeds are in Russian too, but also happens with English ones. I marked it as major feature as soon making notifications of new messages is very important.
Is this only true for RSS feeds ?
Summary: When new rss messages arrive into subfolder, subfolder's name don't become bold. → When new rss messages arrive into subfolder, subfolder's name doesn't become bold.
Don't know as soon I'm using Thunderbird only for RSS. I had found similar bug https://bugzilla.mozilla.org/show_bug.cgi?id=533928 - it is marked as resolved and seems to appear fixed in Thunderbird 3.2a1 (if I correctly understand 'milestone' field of the bug).
can you try a thunderbird from http://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-comm-central-trunk/ and let me know if it works better ?
Tried this Shredder(removed folder with previous version and copied this one into it). The bug still happens.
From the moment after few days of using Shredder and till now there are no signs of this bug yet.
The bug just happens in Shredder 3.2a1pre. A note: it was the first folder. When the bug was happening more frequently I also noticed that behaviour happens often exacty in the first folder. (Why "first folder"? - It had in happened two distinct installations and their first folders were also different).
Occured one more time - and not in first folder. Are patches were reverted?
Hi, guys. Any news on this issue? For me it was with Tb7, 8, and now with Tb3 (I downgraded some time ago). Already tried "Repair Folder" option and complete RSS account recreating. Nothing helped. If anyone is interested, I can upload whole Feed folder as attachment.
Depends on: 715799
Jens, alta88, can you reproduce?
this is likely fixed with changes that will hit Tb12. with all the recent feed work, this should be closed unless reproducible in Tb14 (current trunk). and due to that, and the fact that there's almost no chance of backporting (unless the drivers want to), new reports of bugs in anything prior to Tb12 should be marked invalid. imo.
Whiteboard: [closeme 2012-06-25]
User Agent: Mozilla/5.0 (Windows NT 6.1; rv:12.0) Gecko/20120424 Thunderbird/12.0 Yep, guys. It seems now Tb's RSS reader works as it should. Thank you so much.
Status: UNCONFIRMED → RESOLVED
Closed: 12 years ago
Resolution: --- → WORKSFORME
Whiteboard: [closeme 2012-06-25]
You need to log in before you can comment on or make changes to this bug.