InformAction Forums

I'm running Firefox 3.6.8 in Windows 7 64-bit and I have the Microsoft Security Essentials running.

I have cleared the browser cache and history and I can't hit the 'enter' key to make new searches work and clicking the 'Search' button doesn't work, either. It works if I go to http://www.google.com/firefox, but then it doesn't work when I try to go to a 'Next' page of searches or if I click on the page number ('2', for example). It only happens with NoScript enabled, including having NoScript the only enabled extension.

This all seemed to start randomly, as I haven't done anything that would affect the browser, other than the recent update to 3.6.8.

Does NoScript show any forbidden script for the Google page when this happen?
Can you see any Error message (red) in Tools|Error Console?

NoScript does not report any blocked scripts on http://www.google.com.

The Error Console reports the following warning:

Warning: Unknown property 'zoom'. Declaration dropped.
Source File: http://www.google.com/
Line: 3

I just installed the latest NoScript update and I am still experiencing the same problem.

Longstanding thread on this ... let me see ...

Follow the links: Google Search Not Working ?

I recently had this same issue.
I cleared Temp files and still nothing. I read in diff site that also mentioned cookies.

In firefox I went to

Tools--Options--Privacy

Press SHOW COOKIES button.

In search box, type Google
Then scroll down and delete the ones listed as google ( I had 13)
Press Close button, Press ok Options window
Now restart Firefox and it should work once again.

Hope this helps.

001100 wrote:I recently had this same issue.
I cleared Temp files and still nothing. I read in diff site that also mentioned cookies.

In firefox I went to

Tools--Options--Privacy

Press SHOW COOKIES button.

In search box, type Google
Then scroll down and delete the ones listed as google ( I had 13)
Press Close button, Press ok Options window
Now restart Firefox and it should work once again.

Hope this helps.

Hot diggity-dang that did it!

Thanks!

I wish I could change this to not RESOLVED.

It turns out that deleting the cookies only fixes it for a short while, then it reverts back to no longer being usable.

I Use Dial wrote:I wish I could change this to not RESOLVED.

Done.

I Use Dial wrote:It turns out that deleting the cookies only fixes it for a short while, then it reverts back to no longer being usable.

Could you try to find out which cookie exactly breaks the dial?
If you could, I could build a surrogate to automatically delete it...

Are you using Session Restore?
Possibility that Session Restore is restoring session cookies (go figure) & that is mucking things up?

(Session Restore does restore session cookies.)