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. `._.-(,_..'--(,_..'`-.;.'