W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2013

Re: ByteString in Web IDL

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Wed, 10 Jul 2013 02:46:15 -0400
Message-ID: <51DD0337.6000706@mit.edu>
To: Norbert Lindenberg <ecmascript@lindenbergsoftware.com>
CC: Jonas Sicking <jonas@sicking.cc>, public-script-coord <public-script-coord@w3.org>
On 7/10/13 2:01 AM, Norbert Lindenberg wrote:
> Changing to ByteString caused a semantic change in XMLHttpRequest: Before the change, to "deflate a DOMString into a byte sequence" was defined as using the low-order byte of each code point, so that "ぇぅご" and "🍇🍅🍔" would be equivalents of "GET". Using ByteString, these should now result in TypeError exceptions. (IE 9 actually sends requests specified as method "ぇぅご", others report a variety of errors, none a TypeError).

Current Gecko (24 and later) should be throwing a TypeError.

> But that's probably not what you meant by "impossible"?

I was confused about DOMString, sorry.  Thought it was an actual Unicode 
string nowadays, not an array of 16-bit units.

Received on Wednesday, 10 July 2013 06:46:48 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:17 UTC