- From: Zack Weinberg <zweinberg@mozilla.com>
- Date: Thu, 3 Jun 2010 12:25:46 -0700
- To: W3C Emailing list for WWW Style <www-style@w3.org>
- Cc: HTML WG <public-html@w3.org>
It's been brought to my attention that HTML5 requires the character U+0000 (NULL) be converted to U+FFFD (REPLACEMENT CHARACTER) at a very early stage of input stream processing. This applies to both the literal character with all bits zero, and the numeric entity �. See http://www.whatwg.org/specs/web-apps/current-work/multipage/parsing.html#preprocessing-the-input-stream (for the literal character) and http://www.whatwg.org/specs/web-apps/current-work/multipage/tokenization.html#tokenizing-character-references (for the entity). CSS2.1 leaves the behavior of U+0000 undefined, both as the literal character and as the backslash escape (\0, \00, etc). I think it would make an awful lot of sense to match HTML5, and I see no downside. I can provide wording if people like the idea, although I would prefer to do so on top of my earlier rewrite of the backslash specification, http://lists.w3.org/Archives/Public/www-style/2010Feb/0221.html . zw
Received on Thursday, 3 June 2010 19:26:26 UTC