- From: Adam Rice <notifications@github.com>
- Date: Thu, 29 Mar 2018 05:06:01 -0700
- To: whatwg/streams <streams@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/streams/pull/911/c377214287@github.com>
> I have seen TransformStream in the spec, but without the browser support I felt not encouraged enough to build the whole demo against it if I cannot test the result in at least Chrome. Is there some kind of shim I could use to patch TransformStreams to browsers which support ReadableStream and WritableStream? It's available in Chrome with the experimental web-platform-features flag enabled: chrome://flags/#enable-experimental-web-platform-features It will hopefully be turned on by default in version 67. https://streams.spec.whatwg.org/demos/transforms/transform-stream-polyfill.js is the outdated but mostly compatible polyfill used by the demos linked from the standard. > Actually, in the case of streams, I hope for for-await-of to enter ECMAScript as this would be the easiest way to iterate over a ReadableStream IMHO. Hopefully you'll be able to use this sooner rather than later: https://github.com/whatwg/streams/issues/778 > Should I make the code changes here in the spec's repository in the demo directory? I also just filed a PR against MDN's repository. I am not shure they support changes there. If we cannot find a compromise with MDN then that would be my preference, yes. -- 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/streams/pull/911#issuecomment-377214287
Received on Thursday, 29 March 2018 12:06:39 UTC