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


Click here to return to the 'Camino is easy' hint
The following comments are owned by whoever posted them. This site is not responsible for what they say.
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 1.5.0.9 ....



[ 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", "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

---
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 "http://images.google.com";

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

[ Reply to This | # ]
more...
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 images.google.[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", "http://images.google.com";);
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 | # ]