- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Thu, 29 Mar 2012 08:57:18 +0200
- To: Anne van Kesteren <annevk@opera.com>
- CC: public-webapps@w3.org, Boris Zbarsky <bzbarsky@mit.edu>, Cameron McCormack <cam@mozilla.com>
On 2012-03-28 20:23, Anne van Kesteren wrote: > On Wed, 28 Mar 2012 20:10:53 +0200, Boris Zbarsky <bzbarsky@mit.edu> wrote: >> On 3/28/12 10:42 AM, Glenn Adams wrote: >>> Any use of DOMString to serve as a holder for arbitrary binary data >>> (including inflating from UTF-8 bytes into 16-bit code units), should be >>> specifically marked as such. >> >> For what it's worth, I would be reasonably happy if we had a >> non-DOMString IDL type to indicate "raw byte sequence" strings, with >> WebIDL defining byte-inflation as the conversion from such things to >> JS strings... > > That's an interesting idea. We could also use that for open()'s method > argument (as doing the opposite, throw for higher than U+00FF, then > deflate). ??? Any valid method name is ASCII only. What's the point in making the API more complicated for this? Best regards, Julian
Received on Thursday, 29 March 2012 06:58:21 UTC