- From: <bugzilla@wiggum.w3.org>
- Date: Wed, 28 Oct 2009 00:06:28 +0000
- To: public-html-bugzilla@w3.org
http://www.w3.org/Bugs/Public/show_bug.cgi?id=8099 Summary: Update 9.5 (Parsing HTML Fragments) for "script data" tokenizer state Product: HTML WG Version: unspecified Platform: All URL: http://www.whatwg.org/specs/web-apps/current- work/multipage/the-end.html#parsing-html-fragments OS/Version: All Status: NEW Severity: normal Priority: P2 Component: HTML5 spec bugs AssignedTo: dave.null@w3.org ReportedBy: matthall@microsoft.com QAContact: public-html-bugzilla@w3.org CC: ian@hixie.ch, mike@w3.org, public-html@w3.org 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 -- Configure bugmail: http://www.w3.org/Bugs/Public/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the QA contact for the bug.
Received on Wednesday, 28 October 2009 00:06:37 UTC