Yes, I think the suggestion was to port from jQuery with consideration
of at least one other working implementation.
/Per
On Thu, May 8, 2008 at 11:02 PM, David Janes <[EMAIL PROTECTED]> wrote:
> And just to jump in here -- surely there's a "done" solution for this that
> we like, can we not jus
Yeah, the major problem of doing a synthetic ondomload event like that
is that you need to instrument all of your pages with that script tag
at the bottom. It's "nicer" to do it via DOM calls because you don't
need to change the markup.
-bob
On Thu, May 8, 2008 at 12:16 PM, Per Cederberg <[EMAIL
Antti Koivisto, one of the Safari browser developers, wrote an
interesting blog entry about page loading recently. It explains some
of the difficulties involved from a browser perspective:
http://webkit.org/blog/166/optimizing-page-loading-in-web-browser/
And a small extract of the most relevant
As I understand things (and I am by no means a JS event sequence
expert), the ordering is as follows:
1. Browser reads page line by line; every time it reads enough lines
to complete a JS statement, it executes that statement; meanwhile, non-
JS content is loaded in to the DOM as it is read
2.
Hi MochiKitters,
I've been using the following trick successfully for a few months now.
It _seems_ to work fine cross-browser and cross platform.
signal(window,'ondomload');
But based on the recent thread about implementing ondomload, I assume
that there must be cases when a simple signal
