W3C home > Mailing lists > Public > public-html@w3.org > October 2009

Re: Issues arising from not reparsing

From: Henri Sivonen <hsivonen@iki.fi>
Date: Mon, 12 Oct 2009 10:32:28 +0300
Cc: "Ian Hickson" <ian@hixie.ch>, "HTMLWG WG" <public-html@w3.org>
Message-Id: <FE26C9B1-FB55-4642-B1F6-9736023F60CF@iki.fi>
To: "Simon Pieters" <simonp@opera.com>
On Oct 12, 2009, at 10:02, Simon Pieters wrote:

> Just the inner escape flag. (I had in mind resetting the inner  
> escape flag in the close tag open state, but I think either works.)

It would be very helpful if this were handled as a set of states and  
without flags editorially. That is, the initial <script> tag would  
move the tokenizer into a state (e.g. 'script text state') that is  
neither the data state nor the same state that <textarea> switches to.

>>  * 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"
>>
>> ...?
>
> The flags should be reset in the "Otherwise, ..." paragraph in the  
> close tag open state.

Furthermore, all the escaping stuff should be removed from non-script  
RCDATA/RAWTEXT elements.

-- 
Henri Sivonen
hsivonen@iki.fi
http://hsivonen.iki.fi/
Received on Monday, 12 October 2009 07:33:05 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 May 2012 00:16:50 GMT