- From: Adam Rice <notifications@github.com>
- Date: Mon, 27 Feb 2017 23:09:19 -0800
- To: whatwg/encoding <encoding@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 28 February 2017 07:10:56 UTC
I uploaded a prollyfill for this functionality at https://github.com/GoogleChrome/text-encode-transform-prollyfill. "prollyfill" because it implements a proposed change to the standard rather than a standard itself. I have tested it in Chrome Canary (with the experimental flag) and Safari Technology Preview. Neither of these browsers have TransformStream, but you can get a polyfill here: https://github.com/whatwg/streams/blob/transform-stream-polyfill/reference-implementation/contrib/transform-stream-polyfill.js. It doesn't yet incorporate the changes to way concurrent use of both APIs is prevented that we've discussed here. This doesn't matter unless you are planning on holding it wrong. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/encoding/issues/72#issuecomment-282960515
Received on Tuesday, 28 February 2017 07:10:56 UTC