Closed Bug 336396 Opened 19 years ago Closed 19 years ago

Deleted messages shown again after feed refresh

Categories

(MailNews Core :: Feed Reader, defect)

x86
Windows XP
defect
Not set
major

Tracking

(Not tracked)

VERIFIED DUPLICATE of bug 258465

People

(Reporter: al_kotov, Assigned: mscott)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.2) Gecko/20060308 Firefox/1.5.0.2 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.8.0.2) Gecko/20060308 Firefox/1.5.0.2 When I delete some read messages from the feed's folder and perform feed refresh Thunderbird 1.5.0.2 show deleted messages again as new/unread (surely messages are provided by the server but Thunderbird should filter out such messages as other software do). It's different from other software's behaviour (for example SharpReader/Snarfer/etc) and very confusing/annoying. Reproducible: Always Steps to Reproduce: 1. Subscribe to some RSS feed. 2. Read few articles and delete them. 3. Refresh the feed. Actual Results: Removed articles appear again. Expected Results: Removed articles must not be shown (even if they still present in the data from server).
*** This bug has been marked as a duplicate of 258465 ***
Status: UNCONFIRMED → RESOLVED
Closed: 19 years ago
Resolution: --- → DUPLICATE
Status: RESOLVED → VERIFIED
dunno what steps you were referring to with your "any feed" comment in bug 258465 comment 149, but the steps in this bug don't reproduce the problem described on an atom feed generated by venus r95, or http://gdata.youtube.com/feeds/base/standardfeeds/most_recent?client=ytapi-youtube-browse&alt=rss using 20080822210110 Thunderbird/3.0b1pre. FFR -- while "any" may be useful speculation when you've tested several cases, it is not a valid quantifier within the steps to reproduce, unless you've actually tested all existing feeds. You do need to specify a failing example, even if any would seem to do with the sample you've tested.
Component: RSS → Feed Reader
Product: Thunderbird → MailNews Core
You need to log in before you can comment on or make changes to this bug.