Issues

• How do atomic writes interact with the connection-level flow control?

  w3c/webtransport#798 · Filter by author vasilvv opened on Sep 28, 2026
  2

• cleanup() closes outgoing datagram writables without checking WritableStreamCloseQueuedOrInFlight

  w3c/webtransport#797 · Filter by author jesup opened on Sep 26, 2026
  1

• pullDatagrams errors datagrams.readable on a zero-length datagram when datagramsReadableType is "bytes"

  Discuss at next meeting
  w3c/webtransport#795 · Filter by author jesup opened on Sep 21, 2026

• "Concepts" section says that there are just two concepts

  Editorial
  w3c/webtransport#793 · Filter by author martinthomson opened on Sep 16, 2026
  1

• Reference specific exporter constructions

  w3c/webtransport#791 · Filter by author martinthomson opened on Sep 16, 2026

• writeDatagrams only resolves back pressure once all buffered datagrams have been sent

  Ready for PR
  w3c/webtransport#787 · Filter by author jan-ivar opened on Sep 1, 2026
  1

  

• Remove [SameObject] from responseHeaders

  Needs testReady for PR
  w3c/webtransport#783 · Filter by author aran opened on Aug 14, 2026
  

• WPT Interop 2026 scope

  Discuss at next meetinginterop 2026
  w3c/webtransport#778 · Filter by author youennf opened on Jul 16, 2026
  2

• Support for reading http status code of WebTransport connect requests

  Discuss at next meeting
  w3c/webtransport#777 · Filter by author petrroll opened on Jul 14, 2026 · Future version
  19

• Update wpt server to latest draft for interop

  interop 2026
  w3c/webtransport#754 · Filter by author jan-ivar opened on Apr 21, 2026
  

• FAST checklist - March 2026 wide review

  w3c/webtransport#750 · Filter by author wilaw opened on Mar 25, 2026

• Seek wide review ahead of Candidate Recommendation

  w3c/webtransport#741 · Filter by author wilaw opened on Mar 11, 2026
  2

• Make WebTransportError constructor compatible

  Needs test
  w3c/webtransport#715 · Filter by author achristensen07 opened on Jan 7, 2026 · Future version
  12

  

• More flexible send orders

  w3c/webtransport#712 · Filter by author vasilvv opened on Dec 15, 2025 · Future version
  12

• Update Charter

  w3c/webtransport#710 · Filter by author wilaw opened on Dec 10, 2025
  1

• Improved congestion control for real-time use cases

  w3c/webtransport#676 · Filter by author jan-ivar opened on Jul 15, 2025 · Future version
  5

• Update our WPTs (meta)

  Ready for PR
  w3c/webtransport#649 · Filter by author jan-ivar opened on Apr 23, 2025 · Proposed Recommendation
  1

  

• Working with servers behind a NAT or on a local network (aka "p2p")

  w3c/webtransport#590 · Filter by author pthatcher opened on Feb 13, 2024 · Future version
  6

• WPT tests are needed for serverCertificateHash feature

  w3c/webtransport#589 · Filter by author javifernandez opened on Feb 8, 2024 · Future version
  6

  

• WPT tests are needed for sendOrder

  Ready for PR
  w3c/webtransport#516 · Filter by author jesup opened on May 23, 2023 · Proposed Recommendation
  7

  

• Node.js support for WebTransport

  w3c/webtransport#511 · Filter by author wilaw opened on May 11, 2023 · Future version
  19

• Should incomingUni/BidirectionalStreams be "owning"?

  Waiting-for-feedback
  w3c/webtransport#507 · Filter by author jan-ivar opened on May 4, 2023 · Future version
  2

• Add WPT to determine whether reception is interleaved

  Ready for PR
  w3c/webtransport#417 · Filter by author jan-ivar opened on Aug 30, 2022 · Future version
  2

  

• Can we feed the [[OutgoingDatagramsQueue]] without prematurely resolving write promises?

  hard
  w3c/webtransport#400 · Filter by author jan-ivar opened on May 24, 2022 · Future version
  7

• Write up a list of usability pitfalls (streams arriving out of order etc)

  EditorialReady for PR
  w3c/webtransport#237 · Filter by author jan-ivar opened on Mar 30, 2021 · Future version
  2