Hello,
I don't know if my way would be called "best practices" but definetly
works as expected.
What I do is whenever I need a fancy feature which needs one or two
plugins, I write a function to start it, that function checks if the
plugin & js code was already loaded, else it blocks the interfac
Sounds like a really good idea.
Rick
> -Original Message-
> From: jquery-en@googlegroups.com [mailto:[EMAIL PROTECTED] On Behalf Of
> GasGiant
> Sent: Monday, August 25, 2008 9:49 AM
> To: jQuery (English)
> Subject: [jQuery] Re: Best practices for including Jquery
&
I load site wide code in the , but since the header is an
include file that is the same for every page, I also use .getScript()
to load page specific code for forms, plug ins, etc. where they are
needed. I put the page content in a with an id element specific
to that page and only load the code i
The only reason to include JavaScript files at the end of the body
instead of the head is because scripts block other downloads. If
you're not experiencing any long page load problems, you can just
leave the includes in the head.
There was a good post about this on the YUI blog:
http://yuiblog.c
I rarely see a situation where the javascript should be or needs to be placed
anyplace else but the head of the document(Well, except for advertising).
But I think it also might have to factor into how a webpage is built. If you
have a header, left nav, right nav, but only need a script for the
5 matches
Mail list logo
