Adding CSS to Camino

[Anthony A]

I use a CSS for add blocking/element hiding in Opera and Safari. It works very well. It's easy to add to those browsers but I'm not sure how to add it to Camino. The CSS is made by Fanboy http://www.fanboy.co.nz/adblock/opera/f ... ements.css. Is it just a matter of placing the file in a specific folder or do I have to add it to another file that already exists? Can it even be done in Camino?

[phiw13]

Camino has an ad-blocking option build-in: Preferences > Web Features pane
It uses a stylesheet that you can find here: right click on Camino.app and choose Show Package Contents, then navigate Contents > Resources > ad_blocking.css (lots of what is covered by that file you link to is covered by Camino's ad-blocking).

You can add to that file if you want, with the caveat that every time you upgrade, the file will be overwritten. In Camino 2.0, the file is 'live', btw. Toggling ad-blocking off/on in the prefpane reloads the file. Handy for experimenting with custom rules for sites.

Otherwise, you can create a userstylesheet in your profile folder. ~/Applications Support/Camino/Chrome. The file must be named userContent.css. This is documented on the help site.

[Anthony A]

Great thanks thats what I needed to know.

[phiw13]

Uncle Asad added to my post above:

Last edited by Uncle Asad on 07 Nov 2009 10:54 am, edited 1 time in total.
Reason: caps matter, too

On OS X, not really. Not for 'chrome', not for 'usercontent.css'

[Uncle Asad]

Huh. OK. I was sure I had seen a case where someone tried to have the wrong case and it failed, but I guess not.

[phiw13]

Huh. OK. I was sure I had seen a case where someone tried to have the wrong case and it failed, but I guess not.

It used to fail, back in the old days. I think - but my memory is not (¡!) improving – Gecko 1.6 'fixed' that by a better communication with OS X internals.

[Anthony A]

I simply replaced the Camino default ad blocker css with the one I linked. I changed the name of it of course so Camino would use it. It works well. The default Camino one is decent but leaves a lot of empty spaces where ads are blocked and didn't collapse the space like the fanboy css does. Also I found the Camino ad block css didn't block text ads in Google and Gmail like fanboy's can. The only hassle will be having to replace the Camino ad block css every time Camino up dates but thats a minor annoyance.

[cflawson]

The only hassle will be having to replace the Camino ad block css every time Camino up dates but thats a minor annoyance.

If you install it as a userChrome.css file, you won't have to replace it every time (although I'm not sure which one would load first and get priority for collapsing whitespace). The only stuff that changes when updating Camino is stuff in the application package itself.

cl

[Anthony A]

If you install it as a userChrome.css file, you won't have to replace it every time (although I'm not sure which one would load first and get priority for collapsing whitespace). The only stuff that changes when updating Camino is stuff in the application package itself.

cl

I put it in the default ad block css so I can easily toggle it on and off when I need to from Camino preferences.