Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I’ve noticed some scripts seem to be called before others on a certain page, I was wondering, what is the specific order for scripts to load? In-page before referenced .js scripts? Are they run in order from first <script> mentioned to last in page, or Is this browser-dependent? How can one make sure that a specific script is first to run in a page?
This is set by W3C in their language specifications. For the HTML 4.01 Specification, for instance, it’s defined in Section 18.2.4 Dynamic modification of documents, item 1.
See above. No, inline and linked scripts are handled identically.
The specifications call for them to be run sequentially from top to bottom. You’ll have to find a browser that implements the language according to specification. I can’t think of any right now that handle SCRIPT tags differently, but I’m sure that is possible.
Another thing to consider is the definition of “run.” That may sound like semantic parsing, but it’s not. JavaScript, like any programming language, is itself designed to behave according to standards. JavaScript is specified in the ECMA-262 5.1 Edition / June 2011 standard to evaluate from left-to-right in Section 7 Lexical Conventions. (Line endings are treated as the left-most character of the next line.) This document also provides conventions for the order in which statements and other operations are evaluated, such as WHILE or FOR statements.
(1) Put it at the top, and (2) choose a browser that implements the language specification.
However, I feel there may be something more behind this question. If you’re trying to stop unexpected code from executing, you’ll have to block it until the ONLOAD event handler registers that the page is complete. (Simply enclose your operations in a function or surround them with an IF to check for a boolean flag, i.e. isLoaded being set true by ONLOAD.) Then, when the ONLOAD event handler fires off, you can kick off operations on your own schedule without having to worry about things like uninstantiated DOM objects.