9096 2010-02-20 11:04:49 +0000 Mapping U+0000 to U+FFFD regresses rendering of pages 2010-10-04 13:54:51 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC All RESOLVED WONTFIX P2 normal --- 1 zcorpan ian ian mike public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 32469 0 zcorpan 2010-02-20 11:04:49 +0000 http://www.depmod.com/albums/some_great_reward/a0470.htm has null chars that appear as question marks in the rendering when using the html5 parser. 32679 1 ian 2010-02-25 11:19:44 +0000 EDITOR'S RESPONSE: This is an Editor's Response to your comment. If you are satisfied with this response, please change the state of this bug to CLOSED. If you have additional information and would like the editor to reconsider, please reopen this bug. If you would like to escalate the issue to the full HTML Working Group, please add the TrackerRequest keyword to this bug, and suggest title and text for the tracker issue; or you may create a tracker issue yourself, if you are able to do so. For more details, see this document: http://dev.w3.org/html5/decision-policy/decision-policy.html Status: Rejected Change Description: no spec change Rationale: This is a known issue. The treatment of U+0000 as something other than U+0000 is intentional as defence-in-depth against a variety of attacks based on code that treats U+0000 as a string terminator. As such, unless it breaks a significant number of pages, I think we're better off with this behaviour, even if it does affect a few pages in the meantime.