[Bug 11298] Surrogate catching doesn't belong in input stream preprocessing

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

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

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

--- Comment #4 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-02-09 00:29:09 UTC ---
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: Partially Accepted
Change Description: see diff given below
Rationale: I've changed the parser to not do this stuff with surrogates (except
for numeric char refs) — however, this is not because I think we should allow
surrogates here, but because the DOM APIs shouldn't be letting surrogates into
the platform, regardless of whether it's a parser API or some other API.

That JS uses UTF-16 is a design mistake, but not one that we need to propagate
to the entire platform, nor one that we need to enforce on other languages
should they ever be added to the platform. As such, the DOM should be
Unicode-clean, not UTF-16.

-- 
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 Wednesday, 9 February 2011 00:29:11 UTC