7792 2009-10-02 09:08:45 +0000 async on inline script is gratuitously backwards-incompatible, should be ignored 2010-10-04 13:58:17 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC All CLOSED FIXED NE P2 normal --- 1 hsivonen ian bkuhn ian jonas mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 28003 0 hsivonen 2009-10-02 09:08:45 +0000 Since inline scripts are immediately available, it seems that the only effect the async attribute has on them is that document.write() blows away the document instead of writing to the stream. While this would allow an optimization in speculative parsing, it seems dangerous to introduce a situation where people developing on an older browser could blow away the document without any other benefit than a timing optimization. Furthermore, if one wanted to deliberately promise not to use document.write() but one otherwise wanted the usual scripting semantics, it would be less confusing to have an attribute like "nodocumentwrite" which would make a parser with speculation capability not start a new speculation. (I'm not actually suggesting such an attribute here, because I don't have data about the perf effect of the potential optimization.) Thus, even if a minor opportunity for optimization is lost, it would seem prudent to ignore async on inline scripts like defer is ignored on inline scripts. 28148 1 contributor 2009-10-09 04:36:33 +0000 Checked in as WHATWG revision r4098. Check-in comment: Dramatically simplify <script defer> and <script async> handling. http://html5.org/tools/web-apps-tracker?from=4097&to=4098