Google Reader causing tabs to not respond




Tabbed Browser
12 years ago
8 years ago


(Reporter: Berkana, Unassigned)


Firefox Tracking Flags

(Not tracked)


(Whiteboard: [CLOSEME 2010-11-15])



12 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv: Gecko/20061204 Firefox/
Build Identifier: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv: Gecko/20061204 Firefox/

In a window with many other tabs open, upon reaching the bottom of a long list of items in Google's RSS reader, the page becomes unresponsive; clicking on links won't work, clicking on other tabs changes the page title, but the tabbed pages won't come forward. Instead, the page remains stuck on Google Reader.

Reproducible: Sometimes

Steps to Reproduce:
1.Open up google reader page (presumably, you've subscribed to many RSS feeds)
2. Click on "All Items"
3. scroll through until you reach the end of the items
4. Sidebar indicates that there are still some items unread, though you've reached the bottom of the list; attempt to click on one of the listings in the sidebar to see unread items.
Actual Results:  
The window appears to be unresponsive, except that clicking on other tabs changes the title bar; the tabbed pages don't show up themselves.

Expected Results:  
The page, and all tabs, should continue to behave as they normally do, and respond to clicks.

Having tried to reproduce the problem, and finding that it didn't happen just now, I suspect that this problem only happens when Google Reader updates one of the RSS feeds while I'm reading the listings. This never happened when I read the listings one feed at a time--only when I read them in the "List All" format.

Comment 1

12 years ago
I suspect that this is the same issue that's reported in bug 337786; I saw the same behavior today, three times, when using Google Reader.  I doubt it's specific to GR, though -- my suspicion is that it's related to the background Ajax calls being made messing with the focus and UI somehow, but I don't know.
This bug was reported using Firefox 3.0 or older, which is no longer supported. The bug has also not been changed in over 500 days and is still in UNCO.
Reporter, please retest this bug in Firefox 3.6.10 or later using a fresh profile, If you still see this problem, please update the bug. If you no longer see the bug, please set the resolution to RESOLVED, WORKSFORME.

This is a mass search of unconfirmed bugs that have no activity on them, so if you feel a bug was marked in error, just remove the CLOSEME comment in the whiteboard within the next month.
Whiteboard: [CLOSEME 2010-11-15]
No reply, INCOMPLETE. Please retest with Firefox 3.6.12 or later and a new profile ( If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.