9281 2010-03-19 16:51:48 +0000 The sentence "When used to include data blocks..." would benefit from clarification: "When used to include non-JavaScript data blocks..." 2010-10-04 14:57:22 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#script P3 normal LC 1 contributor ian ayg ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 33715 0 contributor 2010-03-19 16:51:48 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#script Comment: The sentence "When used to include data blocks..." would benefit from clarification: "When used to include non-JavaScript data blocks..." Posted from: 213.123.197.180 33718 1 ayg 2010-03-19 17:19:41 +0000 *** Bug 9282 has been marked as a duplicate of this bug. *** 33719 2 ayg 2010-03-19 17:22:05 +0000 See IRC logs for context: http://krijnhoetmer.nl/irc-logs/whatwg/20100319#l-521 The difference between "dynamic script" and "data blocks" is not clear. I'm not sure why the distinction exists -- can't data blocks be treated identically to inline scripts for the spec's purpose? 34267 3 contributor 2010-03-31 20:36:28 +0000 Checked in as WHATWG revision r4926. Check-in comment: Try to clarify that this is mutually exclusive with the previous paragraph http://html5.org/tools/web-apps-tracker?from=4925&to=4926 34268 4 ian 2010-03-31 20:43:30 +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: Partially Accepted Change Description: see diff given above Rationale: I don't know how to make this clearer. I don't think we should ignore the distinction, in part because otherwise people won't think that it's ok to use it for this purpose, and in part because we need the distinction to ban src/async/defer from <script>s for data blocks.