[Bug 9659] Initial U+0000 should not set frameset-ok to "not ok"


--- Comment #35 from Ian 'Hixie' Hickson <ian@hixie.ch> 2010-11-02 01:52:44 UTC ---
(In reply to comment #34)
> I guess we can make them get swallowed if you like. That would just be a change
> to the "in body" and "in select" insertion modes to ignore the token in that
> case. However, that conflicts with the desire expressed in comment 16.

Actually I've done this anyway, since in the "in body" you have to do special
work for U+0000 anyway to make sure it is treated like a space character for
frameset-ok purposes, and "in select" is rare. So U+0000 just disappears when
used in content now.

> > Why not add the U+0000 to U+FFFD mapping to the "text" insertion mode?
> See comment 16.

There didn't seem to be any particular advantage to doing this one way or the
other, so I left this in the tokenizer where most of the U+0000 work now lives.
(The less per-character stuff we can do in the tree builder the better, IMHO;
the whole point of the tokenizer is to deal with characters.)

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 Tuesday, 2 November 2010 01:52:46 UTC