Submit Hint Search The Forums LinksStatsPollsHeadlinesRSS
14,000 hints and counting!

Revert Google Images to its previous format Web Browsers
For those of you that haven't noticed, Google recently updated its image search to a flashy CSS site. However, as nice as it looks, a lot of fuctionality has been lost. I use Google Images to search for album art, and it's handy to be able to see the domain and image size of all the results without having to hover over each thumbnail.

The fix? With SafariStand (and other plugins like Saft may provide the same), go to SafariStand Settings » Site Alteration, and enable it for Next, check the Alter box for Javascript and leave Javascript disabled. It should look like this when you're done.

Next time you do a google search, google will automatically redirect you to the javascript-free version, and all is good!

[robg adds: This is a very annoying change; flashy mouseover effects come at the expense of easy usability. You can fix the site in OminWeb using the Page Info section (Command-I), and in Firefox using probably any of many extensions -- I tried QuickJava, which gives you a global Javascript on/off button on the toolbar (just click it before running an image search). Unfortunately, I couldn't find a similar tool for Camino -- if you know of a way to quickly toggle Javascript on and off in Camino, please post in the comments.]
  • Currently 2.25 / 5
  You rated: 5 / 5 (4 votes cast)

Revert Google Images to its previous format | 24 comments | Create New Account
Click here to return to the 'Revert Google Images to its previous format' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
Camino is easy
Authored by: simbalala on Jan 31, '07 08:21:35AM

As is Firefox, no extensions needed.

In a new tab or window type about:config

In the window which appears type java into the Filter field, you'll see all options which contain the text java. Double click javascript.enabled and you'll turn off javascript. Double click again to turn it back on.

[ Reply to This | # ]
Camino is easy
Authored by: robg on Jan 31, '07 12:04:38PM

Well, I should have mentioned I knew about about:config ... but I was hoping for something as simple as a toolbar button. I don't want to leave JS off for all sites permanently, nor do I want to open the config each time to toggle it.


[ Reply to This | # ]
Camino is easy
Authored by: osxpounder on Jan 31, '07 01:07:42PM

I agree with Rob. I'd like a "toggle off Javascript for this domain" button, with a noticeable visual difference to show the toggle's state, I guess [unless there's a smarter way to limit it -- what do you think? TLD seemed best at first blush].

With the about:config method, I'll forget I turned off JS for the whole browser, then wonder why YouTube, my bank web site, or something else stopped working.

Using Firefox ....

[ Reply to This | # ]
A specific fix for Camino
Authored by: borgendorf on Jan 31, '07 01:45:12PM
Camino works just like Firefox, by editing a .js file (in Firefox the file is called user.js, Camino calls it prefs.js).

Copy these three lines:

user_pref("capability.policy.policynames", "nojs");
user_pref("capability.policy.nojs.sites", "";);
user_pref("capability.policy.nojs.javascript.enabled", "noAccess");

Quit Camino, navigate to ~/Library/Application Support/Camino/ and open up prefs.js in a text editor.

Paste those three lines onto the bottom and save the file. That's it!


Time flies like an arrow. Fruit Flies like a bananna.

[ Reply to This | # ]

Does not work for me
Authored by: hamarkus on Jan 31, '07 02:07:54PM

Camino overwrites the prefs.js every time it is launched.

[ Reply to This | # ]
Does not work for me
Authored by: simbalala on Jan 31, '07 02:16:39PM
How strange
Authored by: borgendorf on Jan 31, '07 02:31:45PM

How strange, it's working fine for me after numerous Camino restarts. I wonder if it has something to do with me running CamiTools?

Perhaps putting it in user.js will work, as the mozilla link above suggests.

Time flies like an arrow. Fruit Flies like a bananna.

[ Reply to This | # ]
Here's the deal
Authored by: simbalala on Jan 31, '07 03:07:32PM
Add the three lines to both files, user.js and prefs.js (user.js will probably not exist, you'll need to create it).

Also there's an error in the second line posted previously, an extra semicolon. This forum is adding that semicolon.

Remove the semicolon before the final ) in the second line. That is the one immediately after "";

Notice how the board is adding that last semicolon, I didn't type it.

[ Reply to This | # ]
Authored by: simbalala on Jan 31, '07 03:13:35PM

It seems that the existence of a line in the user.js file tells Camino that this line should not be overwritten in the prefs.js file on start-up. That's why the three lines need to be added to both files.

[ and watch out for mystery semicolons in this forum ;-) ]

[ Reply to This | # ]
If only it worked
Authored by: hamarkus on Jan 31, '07 03:36:28PM

That is all nice and well, except that it does not work for me.
Added the three lines to both user.js and prefs.js. On every relaunch, Camino keeps overwriting prefs.js. Naturally javascript remains enabled for Google images search. (I did remove that extra semicolon and I did create that user.js).

Maybe not everything that works for Firefox also works for Camino.

[ Reply to This | # ]
I dunno
Authored by: simbalala on Jan 31, '07 03:50:20PM

It works for me in both Camino and Firefox. The lines in the prefs.js file are moved around (sorted) when Camino or Firefox saves the file so if you add them to the bottom they won't stay there. They'll be sorted upwards.

According to the notes in the prefs.js file in the Firefox folder the file is saved on quit.

[ Reply to This | # ]
Here's a thought
Authored by: simbalala on Jan 31, '07 03:56:34PM

Look for the lines in the prefs.js file (they'll be near the top after Camino saves the file) and make sure you didn't get that bogus semicolon saved in one of your previous tries.

[ Reply to This | # ]
Works, with one more twist
Authored by: hamarkus on Jan 31, '07 04:12:30PM

Found the lines in the prefs.js. What did it, was to add[my country's domain] to it as well.
When using the image search, Google switches from the localised language of google.[my country's domain] back to English which somehow led me to believe that they had not yet localised the URL for the image search but in fact they did.

[ Reply to This | # ]
A specific fix for Camino
Authored by: osxpounder on Jan 31, '07 02:38:36PM

Looks like it'd be a handy tip, if I could find a user.js file. Where do you find it? I don't see it via Spotlight, nor do I see it in ~/Library/Application Support/Firefox, nor in Firefox's package contents.... where is the darn thing?

[ Reply to This | # ]
A specific fix for Camino
Authored by: osxpounder on Jan 31, '07 03:29:50PM
Found the solution. That file wasn't on my system -- yet.

I made one, and put it here:

file://localhost/Users/[my username]/Library/Application%20Support/Firefox/Profiles/7q5z5p7k.default/user.js

The last folder has a gobbledygook name; that's your clue. I changed it in this example, in case mine really means something. Of course I removed my username, too -- but you can probably guess that.

In that folder, I made a text file with TextEdit, saved as user.js, with the following lines:

user_pref("capability.policy.policynames", "nojs");
user_pref("capability.policy.nojs.sites", "";);
user_pref("capability.policy.nojs.javascript.enabled", "noAccess");

Works! What a GREAT TIP!

[ Reply to This | # ]
A specific fix for Camino
Authored by: jolinwarren on Feb 01, '07 03:25:10AM

There is no need to add these lines to the 'prefs.js' file -- this file should never be edited by the user. Adding the lines to the 'user.js' file only (in the same location -- create one if you don't already have it) is sufficient. Camino & Mozilla respect the lines in the 'user.js' file, making editing the 'prefs.js' file unnecessary, and not recommended.

As other posters have noted, you will have to modify the lines given above for your country's local Google domain.

[ Reply to This | # ]
Revert Google Images to its previous format
Authored by: b00le on Jan 31, '07 08:27:03AM

Thanks - that was a most unwelcome change by Google. I was able to do this with PithHelmet, but needed to specify the domain, not - I think there has been another change there, but can't quite figure out what is going on.

[ Reply to This | # ]
Revert Google Images to its previous format
Authored by: jctull on Jan 31, '07 11:41:49AM

PithHelmet Rule Editor with as the matching pattern worked fine for me. I really don't want to disable my gmail functionality.

I simply went to the 'Show Site Preferences' in the PithHelmet menu (either in the main menu bar or burried in the Safari menu item, depending on how yours is set up), clicked on the 'Security' tab and unchecked 'Enable JavaScript.'

This was something I did not realize you could do in PithHelmet. Thanks for pointing out the capability.

[ Reply to This | # ]
Revert Google Images to its previous format
Authored by: @man on Jan 31, '07 01:01:02PM

from teh camino site:

Camino also supports the use of hostperm.1 to block scripts (as well as images and certain other forms of web content). To block items, quit Camino and open the hostperm.1 file in your profile folder using TextEdit or another a text editor. Add items using the format given in the documentation of the "permissions" syntax; note that the blank space between each column is actually a tab. After you finish adding rules, save the file and restart Camino.


basically, go into the hostperm.1 file, type in:

host{this is a tab}script{this is a tab}2{this is a tab}

obviously, {this is a tab} is where you would actually put in a tab stroke.

not a quick and easy, turn on-turn off thing, but it works on google images only, and why would you need to turn that garbage back on?

[ Reply to This | # ]
Does any of the methods work for anybody in Camino?
Authored by: hamarkus on Jan 31, '07 03:45:03PM

Fine, Camino does at least not overwrite this file but javascript is still active on
(and I added[my country's domain] to the file as well).

The only thing that worked for me, was to switch of javascript completely via about:config.

[ Reply to This | # ]
Revert Google Images to its previous format
Authored by: haakin on Jan 31, '07 01:40:08PM
In Opera it's very easy to configure the browser to not use Javascript in a determinate website. In this case, we should open, then Opera -> Quick preferences -> Edit site preferences, after that select the tab Programming (or something like that, I'm using the Spanish version: 'Programación') -it's the 5th tab- and uncheck the use of Javascript.

Once the website is configured, there is no need to repeat the process. The new setup is automatically stored (at least, in my tests).


[ Reply to This | # ]
Revert Google Images to its previous format
Authored by: DMCrimson on Jan 31, '07 09:47:31PM
On firefox, install either greasemonkey or stylish and load this: works on opera too...

[ Reply to This | # ]
Revert Google Images to its previous format
Authored by: Kar98 on Feb 02, '07 06:19:30PM
Firefox for Windows.

Exit Firefox. Go to your Firefox profile. For Windows XP, go to Start/Run and type:
Then click on your profile's folder and open user.js in Notepad (if you can't find it, create a blank text file named user.js). Add these lines at the end of the file:

user_pref("capability.policy.policynames", "nojs");
user_pref("capability.policy.nojs.sites", "";);
user_pref("capability.policy.nojs.javascript.enabled", "noAccess");

Firefox for Mac, same as above, but the file is called prefs.js and it's at
[your hard drive name]/users/[your user name]/library/application support/firefox/profiles/[profilename]/prefs.js

If you use Opera 9 and you want to return to the old design:

* go to Google Images
* right-click and select "Edit site preferences"
* go to the Scripting tab
* uncheck "Enable JavaScript"
* click OK and refresh the page

Internet Explorer
These instructions are for Internet Explorer 7, but should also work for IE6.

* visit Google Images
* go to Internet Options
* in the Security tab, select "Restricted" and click on "Custom level" button
* browse to the Miscellaneous section, enable "Allow META REFRESH" and "Launching programs and files in an IFRAME" (you'll get that these settings will put your computer at risk, which is not really true) and click OK
* click on the "Sites" button and add (the site should already be in the text box).

[ Reply to This | # ]
Revert Google Images to its previous format
Authored by: nowonder on Feb 02, '07 11:33:28PM

Another alternative for Firefox (and probably other browsers) is to switch off the CSS (menu "View" in Firefox).

[ Reply to This | # ]