Re: Intent to ship: TextEncoder.encodeInto() - UTF-8 encode into caller-provided buffer

2019-01-15 Thread Henri Sivonen
On Mon, Jan 14, 2019 at 4:45 PM Boris Zbarsky wrote: > On 1/14/19 4:28 AM, Henri Sivonen wrote: > > This is now an "intent to ship". The feature landed in the spec, in > > WPT and in Gecko (targeting 66 release). > > Where do other browsers stand on this feature, do you know? I see active involve

Re: Intent to ship: TextEncoder.encodeInto() - UTF-8 encode into caller-provided buffer

2019-01-14 Thread Boris Zbarsky
On 1/14/19 4:28 AM, Henri Sivonen wrote: This is now an "intent to ship". The feature landed in the spec, in WPT and in Gecko (targeting 66 release). Where do other browsers stand on this feature, do you know? -Boris ___ dev-platform mailing list dev

Intent to ship: TextEncoder.encodeInto() - UTF-8 encode into caller-provided buffer

2019-01-14 Thread Henri Sivonen
This is now an "intent to ship". The feature landed in the spec, in WPT and in Gecko (targeting 66 release). On Mon, Dec 17, 2018 at 9:12 AM Henri Sivonen wrote: > > # Summary > > TextEncoder.encodeInto() adds encoding JavaScript strings into UTF-8 > into caller-provided byte buffers. This is a p