10114 2010-07-08 21:32:51 +0000 Rather than having inline documentation for external scripts, what would be infinitely more useful would be the contents of a script tag with a src attribute should be executed upon the complete loading and execution of the remote script. Therefore <scrip 2010-10-04 14:28:38 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#inline-documentation-for-external-scripts P3 normal --- 1 contributor ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 36699 0 contributor 2010-07-08 21:32:51 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#inline-documentation-for-external-scripts Comment: Rather than having inline documentation for external scripts, what would be infinitely more useful would be the contents of a script tag with a src attribute should be executed upon the complete loading and execution of the remote script. Therefore <script src="blah.js">var b = new blah();</script> would create a new blah() object after loading the blah.js library. The biggest topic for would be whether or not creating var blah = new blah() from within a script tags body would place blah in the window scope or if it would be the same as executing from a function scope wherein it has context from the contents of blah.js. Posted from: 208.79.45.55 38245 1 ian 2010-08-30 18:26:16 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: We can't possibly change that at this point, far too much of the Web depends on this not happening.