Comments on: Inline Script Wrapper and Dependencies

By: DanAtkinson

DanAtkinson — Mon, 11 Aug 2008 09:30:52 +0000

I don’t agree with this at all.

I’m not the world’s biggest fan of doing a load of style in your JS, as that defeats the object of CSS in my opinion.

If you really must do stuff like that in JS, then here’s a simple solution…

On the first line directly after the body tag has been opened, add this:
document.body.className += ‘ hasJS ‘;

Now, in your JS, you could do this:
body.hasJS #red {background-color: #F00;}
body.hasJS #green {background-color: #0F0;}

Isn’t that better? This way you can still have your JS at the bottom of the page, and your elements will be styled correctly.

By: Steve Clay

Steve Clay — Fri, 01 Aug 2008 20:53:46 +0000

I ran into this having a SCRIPT element within a WordPress post. I needed $, but it wasn’t defined until the end of the page. Now a trivial plugin loads directly after jQuery to call any queued functions. Usage is easy:

// setup func to be called later var _waitFor$ = function () { $(doSomething); };

By: AriesBelgium

AriesBelgium — Wed, 30 Jul 2008 18:51:29 +0000

Sorry, typo:
$(“#green”).css(‘background-color’,'green’);

By: AriesBelgium

AriesBelgium — Wed, 30 Jul 2008 18:43:08 +0000

Okay, this is kinda of a paradox. He would put the JS on the bottom of the page because that would give him a performance boost (at least that is what YSlow is claiming) but then he creates an extra loop which isn’t actually necessary because he could put the code that he does inline now right after loading jQuery. His solution would be more system intensive than loading the JS in the head-section.

And what’s wrong with:
$(“#green”).css(‘background-color’:'green’);?