- From: Ian Hickson <ian@hixie.ch>
- Date: Fri, 16 Oct 2009 21:58:15 +0000 (UTC)
- To: Simon Pieters <simonp@opera.com>
- Cc: Henri Sivonen <hsivonen@iki.fi>, HTMLWG WG <public-html@w3.org>
So the proposed changes to the spec are:
* in the Data state, while the escape flag is true, if the last start
tag token emitted had the tag name "script", if you consume "t" or
"T", then:
if the previous characters were an ASCII case-insensitive match for
"<scrip", then set the inner escape flag to true,
if the previous characters were an ASCII case-insensitive match for
"</scrip", then set the inner escape flag to false,
* whenever the escape flag is set to false (-->), also set the
inner-escape flag to false,
* for "<" in the Data state, you always switch to the Tag open state, and
* in the RCDATA/RAWTEXT bit at the top of the Close tag open state, add
to the end of the first paragraph "or they are but the escape flag is
true and either the last start tag token emitted did not have the tag
name "script", or it was and the inner-escape flag is true"
* in the RCDATA/RAWTEXT bit at the top of the Close tag open state, if
the "Otherwise" clause is going to be followed, reset the escape flag
to false.
If so, then I'll just make a new set of states, like Henri suggested.
Maybe even tokeniser states.
We still need the <!--/--> magic nonsense in other elements, right? Like
<textarea><!--</textarea>--></textarea>?
--
Ian Hickson U+1047E )\._.,--....,'``. fL
http://ln.hixie.ch/ U+263A /, _.. \ _\ ;`._ ,.
Things that are impossible just take longer. `._.-(,_..'--(,_..'`-.;.'
Received on Friday, 16 October 2009 21:46:45 UTC