Client Side Web Development

Re: Timing of javascript execution

NC01 — Fri, 23 May 2008 12:25:09 GMT

In my experience, attaching a process to the window.onload event has always worked.

NC...

Re: Timing of javascript execution

Zeevik — Thu, 22 May 2008 17:07:13 GMT

jamesqua:
The answer to your second question is yes. It will replace any other functions hooked to that event. Here is a way to attach multiple events. Perhaps there is a better way to go about this. What exactly are you trying to achieve?

Thanks, this is exactly the answer to what I was asking about.

NC01:
What are you going to sue me if it doesn't? There is no way to guarantee of that. That is just not the way browsers work.

No, I'm not american - I'm not into sueing. The reason I was asking if "you guarantee" is because I heard from several people that attaching a script to the onload event doesn't guarantee that the page (with all its elements) is going to be fully loaded by the time the script executes. So rephrasing the "you guarantee" would be "does it usually/always work, from your experience?"

NC01:
So just put all other scripts/functions that you want in the onload in there.

Unfortunately, that is not always possible For example, in my case, I'm dealing with rather large e-commerce application that uses xml templates to generate web pages.

Re: Timing of javascript execution

NC01 — Thu, 22 May 2008 16:41:52 GMT

Zeevik:

Are you saying it's guaranteed to run only when the page is fully loaded?

What are you going to sue me if it doesn't? There is no way to guarantee of that. That is just not the way browsers work.

Zeevik:

Also, will it replace any other scripts/functions that are currently hooked up to the window onload event? If so, is there a way to append instead of replacing?

Yes it will replace any other scripts/functions that are currently hooked up to the window onload event. So just put all other scripts/functions that you want in the onload in there.

NC...

Re: Timing of javascript execution

jamesqua — Thu, 22 May 2008 16:41:36 GMT

The answer to your second question is yes. It will replace any other functions hooked to that event. Here is a way to attach multiple events. Perhaps there is a better way to go about this. What exactly are you trying to achieve?

Re: Timing of javascript execution

Zeevik — Thu, 22 May 2008 16:22:33 GMT

Are you saying it's guaranteed to run only when the page is fully loaded?

Also, will it replace any other scripts/functions that are currently hooked up to the window onload event? If so, is there a way to append instead of replacing?

Re: Timing of javascript execution

NC01 — Thu, 22 May 2008 16:06:13 GMT

NC...

Re: Timing of javascript execution

Zeevik — Thu, 22 May 2008 15:57:27 GMT

Yes, I am aware of "onload", but from what I know using it with "body" doesn't guarantee that the page is fully loaded.

And also it is supported only by: <body>, <frame>, <frameset>, <iframe>, <img>, <link>, <script>. (at least according to w3schools)

Re: Timing of javascript execution

jamesqua — Thu, 22 May 2008 15:51:01 GMT

You can use the onload event to fire the JavaScript after an object has loaded.

Timing of javascript execution

Zeevik — Thu, 22 May 2008 15:45:13 GMT

Hello,

Is there a way to force a javascript to execute at certain point in time during page rendering/loading?

i.e.: let's say I want the script to run only after the page is fully loaded/rendered. Or, I want it to run only after a table is fully loaded. etc.

Thanks.