W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > May 2011

[Bug 12100] UAs do not actually convert DOMStrings to sequences of Unicode characters. Test case: data:text/html,<!doctype html><script>document.documentElement.title = "\ud800"; alert(document.documentElement.title.charCodeAt(0));</script> Expected 65533, got 5529

From: <bugzilla@jessica.w3.org>
Date: Wed, 04 May 2011 22:55:30 +0000
To: public-html-bugzilla@w3.org
Message-Id: <E1QHkyg-0005te-6d@jessica.w3.org>
http://www.w3.org/Bugs/Public/show_bug.cgi?id=12100

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |ian@hixie.ch

--- Comment #3 from Ian 'Hixie' Hickson <ian@hixie.ch> 2011-05-04 22:55:29 UTC ---
Agreed that DOM-tree-manipulating APIs should work in 16bit codepoints. The
intent of this change was to make sure that APIs like window.alert() worked
with Unicode, and that all the various algorithms in the spec worked with
Unicode, etc. We don't want algorithms that talk about doing things character
by character breaking every time an astral plane character gets involved
because they get split in two.

Does anyone have any suggestions for how to do this without having to go down
every single method and attribute or every single algorithm saying which ones
are operating in Unicode space and which are operating in UTF-16 word space?

-- 
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, 4 May 2011 22:55:33 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:09 UTC