|
|
A specific fix for Camino
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", "http://images.google.com"); 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! Source: http://googlesystem.blogspot.com/2007/01/getting-old-google-image-search-back.html ---
Does not work for me
Camino overwrites the prefs.js every time it is launched.
Does not work for me
How strange
How strange, it's working fine for me after numerous Camino restarts. I wonder if it has something to do with me running CamiTools?
Here's the deal
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 "http://images.google.com" Notice how the board is adding that last semicolon, I didn't type it.
more...
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.
If only it worked
That is all nice and well, except that it does not work for me.
I dunno
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.
Here's a thought
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.
Works, with one more twist
Found the lines in the prefs.js. What did it, was to add images.google.[my country's domain] to it as well.
A specific fix for Camino
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?
A specific fix for Camino
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", "http://images.google.com"); user_pref("capability.policy.nojs.javascript.enabled", "noAccess"); Works! What a GREAT TIP!
A specific fix for Camino
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. |
SearchFrom our Sponsor...Latest Mountain Lion HintsWhat's New:Hints1 new Hints in the last 24 hoursComments last 2 daysNo new commentsLinks last 2 weeksNo recent new linksWhat's New in the Forums?
Hints by TopicNews from Macworld
From Our Sponsors |
|
Copyright © 2014 IDG Consumer & SMB (Privacy Policy) Contact Us All trademarks and copyrights on this page are owned by their respective owners. |
Visit other IDG sites: |
|
|
|
Created this page in 0.09 seconds |
|