8912 2010-02-10 00:15:41 +0000 Why can't defer be used on inline scripts? If the script execution is slow (which can include loading of preceeding style sheets), the browser will have to wait until it can continue parsing and start downloading subsequent external resources. 2010-10-04 14:55:44 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#script P3 normal LC 1 contributor ian hsivonen ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 31688 0 contributor 2010-02-10 00:15:41 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#script Comment: Why can't defer be used on inline scripts? If the script execution is slow (which can include loading of preceeding style sheets), the browser will have to wait until it can continue parsing and start downloading subsequent external resources. Posted from: 81.216.154.159 31694 1 hsivonen 2010-02-10 07:50:15 +0000 Honoring defer on inline scripts was deemed to be a problem due to existing content calling document.write() there. 32071 2 ian 2010-02-14 11:18:59 +0000 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: Browsers already parse ahead of inline <script>s optimistically, so it doesn't stop that. As Henri says, this was considered (in fact, it was even specced for a while) and ended up being removed because of some really strange interactions between <script>, the parser, document.write(), and innerHTML.