[Bug 9096] Mapping U+0000 to U+FFFD regresses rendering of pages

http://www.w3.org/Bugs/Public/show_bug.cgi?id=9096


Ian 'Hixie' Hickson <ian@hixie.ch> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |WONTFIX




--- Comment #1 from Ian 'Hixie' Hickson <ian@hixie.ch>  2010-02-25 11:19:44 ---
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.


-- 
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 Thursday, 25 February 2010 11:19:46 UTC