8099 2009-10-28 00:06:28 +0000 Update 9.5 (Parsing HTML Fragments) for "script data" tokenizer state 2010-10-04 14:47:29 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified All All RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/multipage/the-end.html#parsing-html-fragments NE P3 normal LC 1 matthall ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 29144 0 matthall 2009-10-28 00:06:28 +0000 Step #4.1 of Section 9.5 (Parsing HTML Fragments) says: "If it is a style, script, xmp, iframe, noembed, or noframes element: Switch the tokenizer to the RAWTEXT state." However, the removal of the content model state, and the corresponding addition of the "script data" state to the tokenizer have made this outdated. I think you need to split "style" out here and say that a "style" tag requires that you switch the tokenizer to the "Script Data" state, which also matches the new tree construction algorithm (9.2.5.7 The "in head" insertion mode for a start tag named "script). -Matt 29231 1 matthall 2009-10-30 19:32:22 +0000 Sorry, I meant "script" tags, not "style" tags! 30372 2 ian 2010-01-04 11:03:01 +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: Accepted Change Description: see diff given below Rationale: Done, but it actually makes no practical difference. 30376 3 contributor 2010-01-04 11:27:23 +0000 Checked in as WHATWG revision r4457. Check-in comment: Update the fragment parsing algorithm to handle <script> more theoretically properly. And mention a quicker implementation strategy. http://html5.org/tools/web-apps-tracker?from=4456&to=4457