- From: Joshua Bell <jsbell@chromium.org>
- Date: Wed, 14 Mar 2012 16:12:03 -0700
On Wed, Mar 14, 2012 at 3:53 PM, Glenn Maynard <glenn at zewt.org> wrote: > > It's more than a naming problem. With this string API, one side of the > conversion is always a DOMString. Base64 conversion wants > ArrayBuffer<->ArrayBuffer conversions, so it would belong in a separate API. > Huh. The scenarios I've run across are Base64-encoded binary data islands embedded in textual container formats like XML or JSON, which yield a DOMString I want to decode into an ArrayBuffer.
Received on Wednesday, 14 March 2012 16:12:03 UTC