Full Unicode strings strawman

[Brendan Eich]

On May 16, 2011, at 2:07 PM, Boris Zbarsky wrote:

> That said, defining JS strings and DOMString differently seems like a recipe for serious author confusion (e.g. actually using JS strings as the DOMString binding in ES might be lossy, assigning from JS strings to DOMString might be lossy, etc).  It's a minefield.

Plus, people stuff random data into JS strings, which so far have not UTF-16 validated or indexed, and they could read back arbitrary uint16s in a row.

Breaking this seems web-breaking to me, from what I remember. It's impossible to detect statically (early error).

/be