This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10114 - 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
Summary: Rather than having inline documentation for external scripts, what would be i...
Status: RESOLVED WONTFIX
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-08 21:32 UTC by contributor
Modified: 2010-10-04 14:28 UTC (History)
4 users (show)

See Also:

Attachments

Description contributor 2010-07-08 21:32:51 UTC 
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
Comment 1 Ian 'Hixie' Hickson 2010-08-30 18:26:16 UTC 
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.