Execution order of onModuleLoad and body.onload

I am a bit confused by GWT's documentation of its bootstrap order:
http://code.google.com/webtoolkit/doc/latest/DevGuideOrganizingProjects.html#DevGuideBootstrap
which says or at least suggests that onModuleLoad is called before
body.onload:
10. externalScriptOne.js completes. The document is ready, so
onModuleLoad() fires.
12. body.onload() fires, in this case showing an alert() box.

It also says:
"Once the GWT selection script has started, its onModuleLoad() can be
called at any point after the outer document has been parsed."

I don't know if it's only me, but I think the documentation could be
clearer on the call order of the two functions.

However, as Thomas Broyer says in this post:
http://groups.google.com/group/google-web-toolkit/browse_thread/thread/4df63848f86ce5a2/a7dab35743346d41?lnk=gst&q=body+onload#a7dab35743346d41
and as my tests also show, onModuleLoad is always called after
body.onload.

So, can one rely on onModuleLoad being called after body.onload?

--
You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group.
To post to this group, send email to google-web-toolkit@googlegroups.com.
To unsubscribe from this group, send email to google-web-toolkit+unsubscribe@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.