Page 1 of 1

Google news freezes on Nightly

Posted: Tue Aug 02, 2011 7:59 pm
by firebo14
About weeks ago, it worked ok.

Right now, firefox will freeze and lag if i enable scripts of google.com, if i disable, works fine. Hope u guys fix this.

Im using:
Firefox Nightly 8.0a1 (2011-08-02)

:]

Re: Google news freeze.

Posted: Tue Aug 02, 2011 10:55 pm
by firebo14
Noscript 2.1.2.5rc1

Re: Google news freeze.

Posted: Wed Aug 03, 2011 10:04 am
by Giorgio Maone
I cannot reproduce with latest development build, can you?
Does it happen also if you disable every extension except NoScript?

Re: Google news freeze.

Posted: Wed Aug 03, 2011 3:37 pm
by firebo14
Ok, nevermind, it now works ok. I update Nightly today to:

8.0a1 (2011-08-03)

:]

Re: [RESOLVED,INVALID] Google news freeze.

Posted: Sat Aug 06, 2011 1:30 am
by rockachu2
HAppens to me, firefox 8.0a1 2011-8-05
freezes news with no response.
only happens with noscript enabled.

Re: [RESOLVED,INVALID] Google news freeze.

Posted: Sat Aug 06, 2011 3:53 am
by AndyY
I don't agree with "RESOLVED,INVALID"

Firefox Nightly 8.0a1 (2011-08-05) and NoScript 2.1.2.6rc4.
AdBlockPlus and Ubuntu extensions disabled.
Fresh browser, go to news.google.com and mouse pointer moves, but firefox otherwise unresponsive to all clicks, scroll wheel, elevator bar, cursor doesn't change when hovering over links. Firefox menus all dead. Only thing that works is the "close" button.
Disable noscript and then news.google.com operates. Lots of pop-up previews when you hover, which seems to be what it is that is new at google news.

Re: [RESOLVED,INVALID] Google news freeze.

Posted: Sat Aug 06, 2011 6:10 am
by Giorgio Maone
OK, I could reproduce by selecting "U.S." as the news source (couldn't with my default, Italy), so I suppose it's triggered by this new preview feature which is offered in some regions only, it seems.

Investigating...

Re: Google news freezes on Nightly

Posted: Sun Aug 07, 2011 12:35 am
by Giorgio Maone
Filed https://bugzilla.mozilla.org/show_bug.cgi?id=677050 about this.

A tentative work-around is provided by latest development build 2.1.2.6rc6