Killing Google Instant (November 3rd, 2011 edition)

This morning, I woke up to find that Google had made another change which broke my solution for disabling Google Instant badly enough for Firefox to give me a blank page. Since Google seems to delight in trying to force people to log in to disable their misfeatures and most of the solutions are out of date, I thought I’d share what I came up with.

Please note that, in Chrome, I just disable JavaScript on Google sites and use the Incognito Window as a way to fake “Temporarily Allow” for parts of the site with no Basic Mode. (enabling JavaScript in an Incognito Window via the address bar icon will be forgotten along with the rest of your browser history) This solution is for Firefox, where I’m used to having everything Just Work™.

First, get NoScript. You can still turn off the JavaScript whitelisting using the “globally allow” option if it bothers you but this solution uses its surrogates system to patch the Google Search page.

Second, open up either your user.js or about:config. We need to create two new string keys. (Thanks to al_9x for the code I started from. I’ve modified it to also work on

Here are the surrogates you need to add. (My apologies for the form they’re in. WordPress insisted on mangling them if I embedded the code right in the post in a prettier form.)

CC BY-SA 4.0 Killing Google Instant (November 3rd, 2011 edition) by Stephan Sokolow is licensed under a Creative Commons Attribution-ShareAlike 4.0 International License.

This entry was posted in Geek Stuff. Bookmark the permalink.

1 Response to Killing Google Instant (November 3rd, 2011 edition)

  1. Nesetalis says:

    Should be noted, there is also NotScripts for chrome. I didn’t leave firefox for chrome until i had both an adblock and noscript equivalent.

Leave a Reply

Your email address will not be published. Required fields are marked *

By submitting a comment here you grant this site a perpetual license to reproduce your words and name/web site in attribution under the same terms as the associated post.

All comments are moderated. If your comment is generic enough to apply to any post, it will be assumed to be spam. Borderline comments will have their URL field erased before being approved.