Comments on: Obtrusive JavaScript Checker 0.7 – support for JavaScript links, inline event information and summary report

By: Recopilaciones: Lo mejor de los feeds | Por ciento Internet

Recopilaciones: Lo mejor de los feeds | Por ciento Internet — Wed, 03 Dec 2008 22:48:11 +0000

[...] ExtensiÃ³n de firefox para comprobar javascript intrusivo por Robert Nyman [...]

By: Obtrusive Javascript Checker « websenior

Obtrusive Javascript Checker « websenior — Wed, 03 Dec 2008 15:49:03 +0000

[...] la pÃ¡gina de su autor podemos ver su funcionamiento, asÃ como otros soportes de descargas, como en script para [...]

By: 20081127 ?? - ?????? - ???? Jacky’s Blog

20081127 ?? - ?????? - ???? Jacky’s Blog — Thu, 27 Nov 2008 15:11:09 +0000

[...] Obtrusive JavaScript Checker 0.7 Quote: support for JavaScript links, inline event information and summary report [...]

By: Interesting Finds: 2008.11.01~2008.11.07 - gOODiDEA.NET

Interesting Finds: 2008.11.01~2008.11.07 - gOODiDEA.NET — Fri, 07 Nov 2008 00:46:37 +0000

[...] Obtrusive JavaScript Checker 0.7 – support for JavaScript links, inline event information and summary report [...]

By: Obtrusive JavaScript Checker « The Rojo

Obtrusive JavaScript Checker « The Rojo — Fri, 07 Nov 2008 00:21:47 +0000

[...] leave a comment » Day after day, you should realize how important to build unobtrusive JavaScript code. Embracing this concept lets you ensure better code and extremely easier code structure. This is why we are happy to talk here about Robert Nyman who has updated his Obtrusive JavaScript Checker. [...]

By: Obtrusive JavaScript Checker Tool

Obtrusive JavaScript Checker Tool — Wed, 05 Nov 2008 11:00:57 +0000

[...] Full Article [...]

By: Robert Nyman

Robert Nyman — Tue, 04 Nov 2008 19:08:21 +0000

Ionut,

Have the link point to a proper URL, ensuring it works as a regular link should (making it accessible for people with JavaScript disabled, for various reasons).

Then enhance the user experience by adding an onclick event to the link from JavaScript in an external JavaScript file, preventing the default link action, and instead have it perform your desired JavaScript code.

By: Ionut Popa

Ionut Popa — Tue, 04 Nov 2008 17:46:20 +0000

What tehnique do you recommend to be used instead of javascript: links?

By: Ajaxian » Weed Out Obtrusive JavaScript

Ajaxian » Weed Out Obtrusive JavaScript — Tue, 04 Nov 2008 16:52:42 +0000

[...] down the path of providing developers good tools, Robert Nyman of DOMAssistant fame has updated his Obtrusive JavaScript Checker. The tool comes in a couple of different forms including a GreaseMonkey script, a Firefox add-on [...]

By: Robert Nyman

Robert Nyman — Tue, 04 Nov 2008 11:09:00 +0000

HB,

Great idea! I’ve added in the code, it will be in the next release!

By: HB

HB — Tue, 04 Nov 2008 06:51:10 +0000

Curious, is it possible to have the window that sits in the bottom left (“Number of javascript links: … Number of inline events: …”) act as position: fixed instead of absolute? If it’s stuck in front of a link or other element on the page, you can’t get to it without turning off the script and refreshing.

Other than that, I think this is a really cool little script!

By: Obtrusive JavaScript Checker also available as a Ubiquity command - Robert’s talk - Web development and Internet trends

Mon, 03 Nov 2008 23:27:59 +0000

[...] the latest release of Obtrusive JavaScript Checker and its cool information and report features, I got the request to make it as a command for [...]

By: Robert Nyman

Robert Nyman — Mon, 03 Nov 2008 22:50:57 +0000

Florian,

Thanks!
The Firefox extension can be found in the add-ons menu, amongst the other add-ons you have installed. Personally, I’d recommend the Greasemonkey script, since it allows enabling/disabling it without restarting the web browser, and also the possibility to customize it per different domains.

By: Florian

Florian — Mon, 03 Nov 2008 22:45:39 +0000

Hi,
thanks for sharing.
I installed it on Firefox and I am wondering where I can turn it on and off. It does not appear under add-ons or anywhere else.

Thanks,
Florian

By: Robert Nyman

Robert Nyman — Sun, 02 Nov 2008 21:25:43 +0000

Lim,

I see.
Just bear in mind that the code won’t work in IE, but otherwise you should be good to go in other web browsers.

Christian,

Thanks! A REST API complement sounds good, just let me know if you do anything cool with it.

By: christian heilmann

christian heilmann — Sun, 02 Nov 2008 18:03:22 +0000

Nice idea, works pretty cool here. A REST API for this would be cool, too. Maybe I’ll have a go at that.

By: Lim Chee Aun

Lim Chee Aun — Sun, 02 Nov 2008 17:04:12 +0000

Robert,

Ugh, I prefer the bookmarklet thing myself. It’s a good alternative approach for non-GreaseMonkey setups or non-Firefox platforms. Anyway, I’ve made it for my own use. Thanks for the code

By: Robert Nyman

Robert Nyman — Sun, 02 Nov 2008 15:08:08 +0000

Lim,

Ah, I see.
I’d recommend the Greasemonkey approach instead of a bookmarklet, just for the sake of being able to customize domains etc.

Pelle,

Thanks!
I’d recommend Greasemonkey, since it’s then very easy to enable/disable, and to customize for which domains it is being run.

As an Ubiquity command sounds interesting, I’ll think about that! I’ve never developed a Firebug extension, so I’m not really sure what it takes, but it seems a lot easier for the developer to write Greasemonkey scripts rather than Firefox extensions in general.

By: Pelle

Pelle — Sun, 02 Nov 2008 14:09:04 +0000

Nice tool Robert – detecting obtrusive fashions is really important and useful.

Which way is the recommended to use it as? As a greasemonkey script or as an extension?

Some thoughts: Would it be possible/desirable to do a version as a Ubuquity command and/or as a Firebug extension?

Great idea!

By: Lim Chee Aun

Lim Chee Aun — Sun, 02 Nov 2008 11:56:22 +0000

Robert,

Oh, that’s weird. I was trying to make it into a bookmarklet just now, found JS errors from the wrappedJSObject property, removed them and it kind of work without them.