Specification

https://fetch.spec.whatwg.org/#dom-body-textstream and https://w3c.github.io/FileAPI/#text-stream-method-algo

Explainer

No response

Links

• Previous early design review, if any: N/A
• An introduction to the feature, aimed at unfamiliar audiences: A small ergonomic fix for making it easier to stream UTF-8 text without having to create pipes with the stream APIs
• A description of the problems that end-users were facing before this proposal: it's a small dev ergonomics fix- Web Platform Tests: https://wpt.fyi/results/?label=master&label=experimental&aligned&q=textStream

The specification

• Follows the Web Platform Design Principles.
• Includes Security and Privacy Considerations sections based on answers to the Security/Privacy Questionnaire.

Where and by whom is the work is being done?

• GitHub repo: github.com/whatwg/fetch
• Primary contacts: @noamr (Google)
• Organization/project driving the specification: Google
• This work is being funded by:
• Primary standards group developing this feature: WHATWG/W3C
• Group intended to standardize this work: <!-- if different from the current group -->
• Incubation and standards groups that have discussed the design: WHATWG/W3C

Feedback so far

• Multi-stakeholder feedback:
  • Chromium comments: Supportive
  • Mozilla comments: https://github.com/mozilla/standards-positions/issues/1419 (proposed supportive)
  • WebKit comments: https://github.com/whatwg/fetch/pull/1862 (supportive, didn't require an official position)
  • {{...include feedback/review from developers, implementers, civil society, and others}}
• Major unresolved issues with or opposition to this specification: None

You should also know that...

Opening this issue as an FYI for TAG in case other specs that have some ergonomic on top of streams (like the ones patched here) need to be considered as well.

<!-- Content below this is maintained by @w3c-tag-bot -->

---

Track conversations at https://tag-github-bot.w3.org/gh/w3ctag/design-reviews/1236