Closed Bug 435056 Opened 16 years ago Closed 14 years ago

Google Reader unread accounting is wrong

Categories

(Firefox :: General, defect)

3.0 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: dennis.sherod, Unassigned)

References

()

Details

(Whiteboard: [CLOSEME 2010-10-01])

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008051206 Firefox/3.0
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9) Gecko/2008051206 Firefox/3.0

The unread count shown for subscriptions is always a few higher than the actual number of unread articles.  When all articles have been read, several of the subscription will typically show (2) unread.  The "All" collector subscription will show the aggregate of unread articles, i.e. if four subscriptions show 3 unread each the All subscription will show 8 unread, although selecting the subscription will render no unread articles.

Refreash does not zero or otherwise change the counts.

Reproducible: Always

Steps to Reproduce:
1. In Google Reader, create a subscription
2. Mark all articles as read
3. Note that the remaining unread count is not zero
Actual Results:  
The unread count does not match the number of unread articles

Expected Results:  
The count should be 0
I can confirm this on Trunk on Windows 7. I think it might be related to Bug 513082.
Reporter, are you still seeing this issue with Firefox 3.6.9 or later in safe mode? If not, please close. These links can help you in your testing.
http://support.mozilla.com/kb/Safe+Mode
http://support.mozilla.com/kb/Managing+profiles
Whiteboard: [CLOSEME 2010-10-01]
Version: unspecified → 3.0 Branch
No reply, INCOMPLETE. Please retest with Firefox 3.6.10 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.