Contact emails [email protected]
Explainer https://github.com/w3c/webtransport/blob/main/explainer.md Specification https://www.w3.org/TR/webtransport/#dom-webtransportoptions-datagramsreadabletype Summary Adds the WebTransportOptions.datagramsReadableType constructor option. By default, incoming WebTransport Datagrams are exposed through a default ReadableStream . Applications that require BYOB reading can request a readable byte stream by setting datagramsReadableType: "bytes" . Blink component Blink>Network>WebTransport Web Feature ID webtransport Motivation WebTransport Datagrams are discrete messages rather than an undifferentiated byte sequence. A readable byte stream can lose empty Datagrams and can lose message boundaries when BYOB reads use a minimum byte count spanning multiple Datagrams. Making a default ReadableStream the default preserves Datagram boundaries and empty Datagrams. Applications that benefit from BYOB allocation control can explicitly opt into the byte-stream behavior. Initial public proposal No information provided Goals for experimentation None Requires code in //chrome? False Tracking bug https://issues.chromium.org/issues/547572475 Availability expectation WebKit has implemented the option and corresponding default-stream behavior in its main branch. Firefox implements the default non-byte stream behavior, although explicit "bytes" /BYOB mode does not yet pass current public WPT runs. Broad availability is expected as implementations converge on the WebTransport specification. Adoption expectation Adoption is expected mainly among WebTransport applications that use BYOB readers or need reliable preservation of Datagram message boundaries. Most applications using ordinary readers require no code changes. Adoption plan Adoption is expected through WebTransport documentation and Interop 2026 visibility. Existing Chromium applications using BYOB readers will need to explicitly set datagramsReadableType: "bytes" when the feature is enabled. Estimated milestones No milestones specified Anticipated spec changes Open questions about a feature may be a source of future web compat or interop issues. Please list open issues (eg links to known github issues in the project for the feature specification) whose resolution may introduce web compat/interop risk (eg, changing to naming or structure of the API in a non-backward-compatible way). None currently anticipated. The option and default-stream behavior are already defined in the WebTransport specification. Link to entry on the Chrome Platform Status https://chromestatus.com/feature/5148774971342848?gate=6221308500246528 This intent message was generated by Chrome Platform Status. -- You received this message because you are subscribed to the Google Groups "blink-dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion visit https://groups.google.com/a/chromium.org/d/msgid/blink-dev/6aa86417.edf999b6.71d4e.0a07.GAE%40google.com.
