Of Jake McGraw
Sent: Tuesday, April 08, 2008 9:20 AM
To: jquery-en@googlegroups.com
Subject: [jQuery] Re: $(window).bind("load",function(){ vs onready
>From the comments on Yahoo Performance Rule # 5
http://developer.yahoo.net/blog/archives/2007/07/high_performanc_5.html:
:: snip ::
This is quite a nice topic for discussion as it touches on various
important theoretical and practical issues.
"All my sites validate perfectly with
>From the comments on Yahoo Performance Rule # 5
http://developer.yahoo.net/blog/archives/2007/07/high_performanc_5.html:
:: snip ::
There are some cases where you wouldn't want your JS at the bottom.
For example, if you were using an "ondomready" event that many of the
js libraries supply, you
On Apr 8, 2008, at 6:23 PM, Jake McGraw wrote:
Regardless of whether it validates, it's considered best practices to
keep all
Regardless of whether it validates, it's considered best practices to
keep all
On Apr 8, 2008, at 6:06 PM, Jake McGraw wrote:
Mixing content and logic, a no no for "standardistas". It really
depends on how much content you have on any given page. I'd suggest
using both the head and "footer" methods to determine what provides
the best end user experience Vs what keeps you
Mixing content and logic, a no no for "standardistas". It really
depends on how much content you have on any given page. I'd suggest
using both the head and "footer" methods to determine what provides
the best end user experience Vs what keeps your pages standard
compliant.
- jake
On Tue, Apr 8,
On Apr 8, 2008, at 6:30 AM, coughlinsmyalias wrote:
I have heard about loading them at the end of the page, I would love
to see statistics on it as well. I understand this all now, I kept
seeing both and I was confused each of them.
When possible JavaScript should be loaded in the end of th
I have heard about loading them at the end of the page, I would love
to see statistics on it as well. I understand this all now, I kept
seeing both and I was confused each of them.
I didnt know that it now waits for .css.
Thank you both Nick and Rob
On Apr 7, 11:21 pm, RobG <[EMAIL PROTECTED]>
On Apr 8, 7:24 am, coughlinsmyalias <[EMAIL PROTECTED]> wrote:
> Thank you! What do you think is better to use? And when would you use
> one compared to another?
There is also the strategy of loading all your script files just
before the closing body tag, at that point you can run whatever scri
well, for example, if you want to do something to your DOM elements
(divs, links, lists etc) and do it as quickly as possible then you
could use document.ready.
if on the other hand you are not in a hurry to change the state of
your DOM elements or the functionality you want to achieve is less
im
ready now waits for both DOM and .css files.
On Apr 8, 4:55 am, MorningZ <[EMAIL PROTECTED]> wrote:
> Your browser window's "Load" event doesn't fire until the document is
> fully loaded (images and all)
>
> The "Ready" event fires when the DOM is ready
>
> More verbose description of "Ready" is
Thank you! What do you think is better to use? And when would you use
one compared to another?
Thanks!
Ryan
ps, ill check out the docs you supplied
On Apr 7, 4:55 pm, MorningZ <[EMAIL PROTECTED]> wrote:
> Your browser window's "Load" event doesn't fire until the document is
> fully loaded (ima
Your browser window's "Load" event doesn't fire until the document is
fully loaded (images and all)
The "Ready" event fires when the DOM is ready
More verbose description of "Ready" is in the docs
http://docs.jquery.com/Events/ready
14 matches
Mail list logo
