The SitePoint Forums have moved.

You can now find them here.
This forum is now closed to new posts, but you can browse existing content.
You can find out more information about the move and how to open a new account (if necessary) here.
If you get stuck you can get support by emailing forums@sitepoint.com

If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.

Not exactly sure what your question is. The synchronicity problem is non-existent: JavaScripts are loaded in series (unlike, say, images) for just that reason - the necessity of keeping absolute control over the availability of program routines & data. The browser won't parse the embedded part of your code until the 'external' file is downloaded and processed; presumably, if your host is down and can't serve the .js file, it won't be sending the containing .html file either. The body object is instantiated as soon as the opening <body> tag is parsed - reference it before, error, anytime after, OK. Lexical errors are self-explanatory (careful!). Never heard of a 'browser include' - did you mean support for <script src="...">? Pretty much a non-issue. The principal timimg issues involve the availability of browser objects, as well as some individual (browser) quirks in making those objects scriptable immediately upon creation. The basic sequencing of script elements is not really (imo) an 'issue' as such, just requires knowing how to write scripts.