W3C home > Mailing lists > Public > whatwg@whatwg.org > March 2008

[whatwg] Tree construction: parse error and plaintext

From: Ian Hickson <ian@hixie.ch>
Date: Thu, 13 Mar 2008 01:22:35 +0000 (UTC)
Message-ID: <Pine.LNX.4.62.0803130122020.25123@hixie.dreamhostps.com>
On Wed, 12 Mar 2008, Thomas Broyer wrote:
>
> In the "in body" insertion mode, shouldn't the "eod-of-file token" case 
> have a special handling of "if the current node is a plaintext element" 
> and not generate a parse error in this case?
> 
> The current behavior is that if you use <plaintext>, you'll have a parse 
> error at EOF. Is this intended?

Yeah. <plaintext> is invalid anyway, and I didn't want to add more stuff 
in the spec just to make it report 1 error instead of 2.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Wednesday, 12 March 2008 18:22:35 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:01 UTC