I disagree. I think this should progress. It doesn't have to add any additional functionality to Typed Arrays. As it stands I would consider it a replacement for the purposes of TextEncoder and TextDecoder APIs. Currently the Mozilla TextDecoder Web API does not accept ASCII as a valid encoding option and defaults to UTF-8, if left unspecified.
On Fri, Jan 10, 2014 at 1:52 PM, Brendan Eich <bren...@mozilla.com> wrote: > Kenneth Russell wrote: > >> Adding a StringView to Typed Arrays would bring along all of the >> complexities of character set encoding and decoding to the Typed Array >> definitions. Typed Arrays were designed to be small, simple, and >> comprehensible enough that they would be easily implementable and >> optimizable. I believe that adding a StringView would contradict these >> goals. >> > > + a lot. > > What can we do to make sure this thing stays dead, if it is dead? Anne may > know some weird W3C protocol trick. ;-) > > /be > > _______________________________________________ > es-discuss mailing list > es-discuss@mozilla.org > https://mail.mozilla.org/listinfo/es-discuss >
_______________________________________________ es-discuss mailing list es-discuss@mozilla.org https://mail.mozilla.org/listinfo/es-discuss
