[whatwg] BinaryEncoding for Typed Arrays using window.btoa and window.atob

Chang Shu cshu01 at gmail.com
Tue Aug 6 13:48:28 PDT 2013

If technically no benefit of passing ArrayBufferView as a 2nd
parameter to atob, I think returning an ArrayBuffer is a good way to
go. Enhancing btoa/atob would be an easy solution while I am open to
enhance the Encoding spec. But it appears to me we have to introduce
another pair of coders, say BinaryDecoder/BinaryEncoder, in addition
to TextDecoder/TextEncode since the signatures of the decode/encode
functions are different.


On Tue, Aug 6, 2013 at 8:28 AM, Kornel Lesiński <kornel at geekhood.net> wrote:
> On Mon, 05 Aug 2013 21:39:22 +0100, Chang Shu <cshu01 at gmail.com> wrote:
>> I see your point now, Simon. Technically both approaches should work.
>> As you said, yours has the limitation that the implementation does not
>> know which view to return unless you provide an enum type of parameter
>> instead of boolean to atob.
> In that case it'd be better to return ArrayBuffer, so the user can wrap it
> in any type they want (including DataView).
> --
> regards, Kornel

More information about the whatwg mailing list