- From: <bugzilla@jessica.w3.org>
- Date: Sun, 23 Sep 2012 21:27:02 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18979 Summary: provide way to guarantee order of execution for async scripts Product: HTML.next Version: unspecified Platform: PC OS/Version: Windows NT Status: NEW Severity: normal Priority: P2 Component: default AssignedTo: dave.null@w3.org ReportedBy: dalimian@gmail.com QAContact: public-html-bugzilla@w3.org CC: plh@w3.org, mike@w3.org currently html 5 spec provides no clean way for a web developer to ensure order of execution of async scripts. One simple solution to achieve this is to introduce a new attribute to script element - "group" the idea is that if one has <script async="async" group="group1" ...></script> then this script will not be executed until any previous scripts of same group have finished executed. This should be simple for browsers to implement,- when the browser is parsing a script with group="groups1" it just checks if it currently has a download or execution of a script belonging to that group, if not, execute. This would make the web lot faster. What you think? to achieve a similar result currently developers are loading the scripts dynamically (thus async) and listening to the onload event for the script, then in the onload they download a dependent script, - this is a huge performance concern cause in this case the downloads happen sequentially and we want the downloads to happen in parallel. -- Configure bugmail: https://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 Sunday, 23 September 2012 21:27:03 UTC