- From: <bugzilla@jessica.w3.org>
- Date: Thu, 08 Jul 2010 21:32:51 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=10114 Summary: 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 Product: HTML WG Version: unspecified Platform: Other URL: http://www.whatwg.org/specs/web-apps/current-work/#inl ine-documentation-for-external-scripts OS/Version: other Status: NEW Severity: normal Priority: P3 Component: HTML5 spec (editor: Ian Hickson) AssignedTo: ian@hixie.ch ReportedBy: contributor@whatwg.org QAContact: public-html-bugzilla@w3.org CC: mike@w3.org, public-html@w3.org 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 -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Thursday, 8 July 2010 21:32:53 UTC