8425 2009-12-03 01:03:50 +0000 Cloning a DOMString with unpaired surrogates should throw SYNTAX_ERR, to allow UAs to serialise structured clones as UTF-8. 2010-10-04 13:59:03 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other RESOLVED WONTFIX http://www.whatwg.org/specs/web-apps/current-work/#structured-clone P3 normal LC 1 contributor ian ap ian mike mjs public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 29901 0 contributor 2009-12-03 01:03:50 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#structured-clone Comment: Cloning a DOMString with unpaired surrogates should throw SYNTAX_ERR, to allow UAs to serialise structured clones as UTF-8. Posted from: 98.248.33.53 30434 1 mjs 2010-01-05 04:06:20 +0000 I disagree with this suggestion: A) DOM Strings (and ECMAScript strings) are everywhere else treated as a sequence of UTF-16 code units and do not fail on bad surrogate pairs. B) "Strings" with possibly invalid surrogate pairs are useful as a workaround to store binary data, in the absence of a proper class for doing so. Thus, throwing an exception in this case would remove useful functionality. C) It's pretty simple to do a almost-UTF-16 --> almost-UTF-8 converter that round trips unpaired surrogates simply by encoding them as if they were individual Unicode characters. Thus, the limitation is not actually required to implement the described behavior. 30721 2 ian 2010-01-07 11:41:21 +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: Concurred with comment 1.