- From: <bugzilla@jessica.w3.org>
- Date: Wed, 20 Jan 2016 20:53:03 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21074 Honore Doktorr <hdfssk@gmail.com> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |hdfssk@gmail.com --- Comment #11 from Honore Doktorr <hdfssk@gmail.com> --- Quick status check: this was resolved FIXED a year ago, but there doesn’t seem to be any reference to it in the HTML 5.1 working draft. If this proposal made it into a spec, does anyone have a link to it? If the proposal was dropped, a WONTFIX resolution would prevent any confusion. from https://www.w3.org/TR/html51/semantics.html#the-script-element on Jan 20 2016 The async and defer attributes are boolean attributes that indicate how the script should be executed. The defer and async attributes must not be specified if the src attribute is not present. There are three possible modes that can be selected using these attributes. If the async attribute is present, then the script will be executed as soon as it is available, but without blocking further parsing of the page. If the async attribute is not present but the defer attribute is present, then the script is executed when the page has finished parsing. If neither attribute is present, then the script is fetched and executed immediately, before the user agent continues parsing the page. … The defer attribute may be specified even if the async attribute is specified, to cause legacy Web browsers that only support defer (and not async) to fall back to the defer behaviour instead of the blocking behaviour that is the default. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 20 January 2016 20:53:25 UTC