Benjamin Gruenbaum
Benjamin Gruenbaum
Couldn't it just be a static function? ``` js MyStreamLibrary.unpackStream(somePromiseForAStream) ```
@eteeselink you're mixing push and pull streams.
Your "fallback" solution makes sense, this can be a disposer pattern but not an actual disposer. Alternatively you can wrap the whole thing in a disposer (instead of just getClient)....
A non compiler generated JS version would be: ```js const composeDisposers = async (outerDisposer, createInnerDisposer) => { const outer = await Promise.resolve(outerDisposer); const outerResult = await outerDisposer._promise; try { const...
It's not standard yet, but in Firefox and Chrome you have https://developer.mozilla.org/en-US/docs/Web/API/MediaStream_API
@iSynaptic what about data attributes?
@jamietre This might not _seem_ important but not encoding HTML entities in attributes can lead to XSS. While it does not seem critical to users like me who do scraping...
Yeah, it doesn't make things _too_ hard to work with (and I ended up using `SetStyles` to resolve the issue). How hard is this to fix? Does it require touching...
I wouldn't remove it at all if I were you, only [Obsolete] it and alias it to addBack :)