1. Well, as it happens, there is still a pref for ReadableStreams. I've been meaning to remove it bug haven't yet. So you can set **javascript.options.streams** to **false** in about:config and see if the behavior changes.
If that doesn't give clear results, I think you'd have to either attach with a debugger, or write an extension to monkeypatch the ReadableStream constructor and some methods to alert before doing their thing.
2. ReadableStream is awfully solid; the most likely issue is that there are some related features we haven't implemented yet: `WritableStream`, `TransformStream`, `.pipeTo` and `.pipeThrough`, and some DOM text-decoding stuff. Mabye the site uses some of these so-far-Chrome-only features if you UA-spoof Chrome?
Bug 1529812 Comment 12 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
1. Well, as it happens, there is still a pref for ReadableStreams. I've been meaning to remove it but haven't yet. So you can set **javascript.options.streams** to **false** in about:config and see if the behavior changes.
If that doesn't give clear results, I think you'd have to either attach with a debugger, or write an extension to monkeypatch the ReadableStream constructor and some methods to alert before doing their thing.
2. ReadableStream is awfully solid; the most likely issue is that there are some related features we haven't implemented yet: `WritableStream`, `TransformStream`, `.pipeTo` and `.pipeThrough`, and some DOM text-decoding stuff. Mabye the site uses some of these so-far-Chrome-only features if you UA-spoof Chrome?