api.WebTransportSendStream - No "proper" getWriter support in Firefox?
Nobody has claimed this yet.
- Dominant language
- JSON
- Stars
- 5.8k
- Forks
- 2.6k
- Avg merge
- 1d 21h
- Merged PRs (30d)
- 186
Description
What type of issue is this?
Incorrect support data (example: BrowserX says "86" but support was added in "40")
What information was incorrect, unhelpful, or incomplete?
BCD argues WebTransportSendStream.getWriter is supported in Firefox and upcoming Safari
What browsers does this problem apply to, if applicable?
Firefox
What did you expect to see?
No support, and/or some note about it
Did you test this? If so, how?
https://searchfox.org/firefox-main/rev/45bf222c56da5257156206bc795b94dcce003b0c/dom/webidl/WebTransportSendReceiveStream.webidl
https://searchfox.org/wubkat/rev/7615722754d2c3ec9ae3385733d0e3a98dc997e3/Source/WebCore/Modules/webtransport/WebTransportSendStream.idl
No getWriter support in either browsers (but only inherited by WritableStream)
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
No response
Do you have anything more you want to share?
I'd probably mark it unsupported and add a note that the support only comes from WritableStream. One could say "partially supported" but it's not machine readable to tell whether the override is implemented or not that way.
MDN URL
https://developer.mozilla.org/en-US/docs/Web/API/WebTransportSendStream
MDN metadata
MDN page report details
- Query:
api.WebTransportSendStream - Report started: 2026-03-01T09:57:50.219Z
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the BCD entry for api.WebTransportSendStream and compare its getWriter data with the Firefox and Safari WebIDL links in the issue. Confirm how inherited WritableStream support is represented, then update the compatibility data and add any appropriate note; run the repository's data validation checks to verify the entry.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, json
- Domain
- documentation, web-dev
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100