-
Notifications
You must be signed in to change notification settings - Fork 27
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Streams #498
Comments
@o-t-w if I understand the scope of the proposal correctly, it's to implement whatwg/streams#980 across browsers. The main tests added for that in web-platform-tests/wpt#15097 are now here: Is that the scope you intended? |
Other recent streams PRs which haven't yet reached all (or in some cases any) browsers, but had strong community driving and involvement, are: |
@domenic can you list the tests for those? |
(with corresponding other items generated from any.js) |
Thank you for proposing Streams for inclusion in Interop 2024. We wanted to let you know that this proposal was not selected to be part of Interop this year. This is because we got many more proposals than we could include in this year's project. Note that individual vendors may nevertheless choose to advance work in this area during the forthcoming year. We would welcome this proposal being resubmitted again next year if necessary. For an overview of our process, see proposal selection. Thank you again for contributing to Interop 2024! Posted on behalf of the Interop team. |
Description
Streams are asynchronously iterable in Node, Deno, Bun and Firefox but not in Chrome or Safari. This means for-await-of loop work for streams in Node/Deno/Bun/Firefox but not Chrome or Safari. This can cause some confusion, as seen here.
This could be broadened if there are other inconsistencies or lacking implementations to do with streams.
Specification
https://streams.spec.whatwg.org/
Open Issues
No response
Tests
No response
Current Implementations
Standards Positions
No response
Browser bug reports
Chromium bug with 46 stars
Developer discussions
No response
Polls & Surveys
No response
Existing Usage
No response
Workarounds
No response
Accessibility Impact
No response
Privacy Impact
No response
Other
No response
The text was updated successfully, but these errors were encountered: