Topic: jquery document.ready (Read 1017 times)
So the answer to your question is probably that people just copy example they see (the long version) and are oblivious to the fact that there's a more concise way to do it.
one waits for the page to complete loading, then do actions in the background. if you put this at the top of a page, with a slow thing, it waits for the page to finish
other fires wherever it hits (blocking, non-async) if you put this at the top of a page, it won't finish rendering until it returns
other fires wherever it hits (blocking, non-async) if you put this at the top of a page, it won't finish rendering until it returns
no, they are functionally identical... both only fire when the 'document' is 'ready'... one is just a shorter way of writing it, but i've seen hundreds of examples all over the web that has the longer version in it.
if these are 100% equivalent, why on earth would anyone ever use the longer version?
$(document).ready(handler)
$(handler)
i really wonder.
As far as I know, nobody uses the longer version. It *is* self-documenting though, which is a plus I guess. $(document).ready(handler)
$(handler)
i really wonder.
one waits for the page to complete loading, then do actions in the background. if you put this at the top of a page, with a slow thing, it waits for the page to finish
other fires wherever it hits (blocking, non-async) if you put this at the top of a page, it won't finish rendering until it returns
other fires wherever it hits (blocking, non-async) if you put this at the top of a page, it won't finish rendering until it returns
if these are 100% equivalent, why on earth would anyone ever use the longer version?
$(document).ready(handler)
$(handler)
i really wonder.
$(document).ready(handler)
$(handler)
i really wonder.
Jump to: