Thanks, that’s an interesting option! However, why I like the JavaScript approach is that it allows me a lot more customization, like the one released in the 0.7 version of Obtrusive JavaScript Checker.

Also, it gives me the possibility to easier turn it into a Greasemonkey script, Firefox extension and a Ubiquiy command at the same time.

Anyway, I think this functionality should be added to the famous Web Developer toolbar by Chris Pedrick into “Information” section — I think that most of tools in this section are in fact “just userstyles” using the same trick as above.

Thanks!

Yes, please be quit.

Told you about Greasemonkey, didn’t I? Much easier to use and customize, and probably the route I’ll take for developing add-ons, instead of full-on Firefox extensions.

Thanks again for sharing

Personally, I’d recommend using the Greasemonkey version instead. That way you can enable/disable it with a single click, customize it for different domains etc.

The Firefox extension was just provided for those who like it, but it’s much more of a hassle to control this with extensions, and to be honest, at the time I didn’t have the time nor motivation to take the extension further.

Try the Greasemonkey version, and I’m sure you will be delighted!

And hush about inline styles, that’s my next one!

I downloaded the XPI version, to take it for a spin, and it turns out that you have to restart the fox every time you need to enable/disable it, which certainly makes the XPI version a little annoying.

I have previously toyed around with Tarantula, and was wondering if I should try to extend it to provide warnings for inline javascript as well as inline styles (as they can be equally deadly). In my little world where rigorous quality control is a must, I’d like to fail builds in CruiseControl when people use inline javascript and inline styles … as well as when I accidentally forget to remove Firebug statements from javascript

I did think of that, but felt that it was somewhat of a different topic. Sure, they’re mostly related, but javascript: links for instance can be bookmarklets and other things, so it’s not that easy to distinguish how to value them.

However, creating one more Greasemonkey script checking for javascript: and # links in general is an easy feat, and most likely something I’ll do in the future! For now, though, the most important thing is getting rid of inline events, I think.