WebTransport Working Group - Activity in 2026
No matches.
Past meetings
Participants
-
2 participants joined.
-
Jianlin Qiu (Intel Corporation) joined.
-
Ling Zhong (Microsoft Corporation) joined.
-
-
16 participants left.
-
Le Zhang (ByteDance) left.
-
Jason Thomas (Datadog) left.
-
Hu Liu (Jiangsu TPBlock Technology Co., Ltd. （江苏第三极区块链科技有限公司）) left.
-
Colin Bendell (Shopify) left.
-
Ilya Grigorik (Shopify) left.
-
Brian Baldino (Cisco) left.
-
quanqing li (ByteDance) left.
-
bdrtc bdrtc (ByteDance) left.
-
Cheng Chen (ByteDance) left.
-
Stefan Pham (Fraunhofer Gesellschaft) left.
-
changqing yan (ByteDance) left.
-
ting xu (ByteDance) left.
-
WEI LI (ByteDance) left.
-
zhi long (ByteDance) left.
-
Ming Yu (ByteDance) left.
-
Jonathan Ding (Intel Corporation) left.
-
-
2 organizations joined.
-
Google LLC joined.
-
Intel Corporation joined.
-
GitHub
w3c/webtransport
-
4 issues opened.
-
Constructor: validate options.headers (steps 30-32) next to the protocols validation w3c/webtransport#805, by @jesup.
-
pullDatagrams steps 7.1.3 and 7.1.4 (elementSize check) can never reject w3c/webtransport#803, by @jesup.
-
WebTransportSendGroup.getStats(): "aggregated stats" is not defined w3c/webtransport#802, by @jesup.
-
-
1 issue closed.
-
Remove [SameObject] from responseHeaders w3c/webtransport#783.
-
-
2 issues received 3 new comments.
-
cleanup() closes outgoing datagram writables without checking WritableStreamCloseQueuedOrInFlight w3c/webtransport#797 (2 comments by @jan-ivar, @saschanaz)
-
WebTransportReceiveStreamStats: define where bytes are "received" so bytesRead <= bytesReceived can be guaranteed w3c/webtransport#804 (1 comment by @jan-ivar)
-
-
3 pull requests opened.
-
Error outgoing datagram writables on teardown instead of closing them w3c/webtransport#801, by @jan-ivar.
-
Omit empty datagrams with a BYOB reader instead of erroring the stream w3c/webtransport#800, by @jan-ivar.
-
Remove [SameObject] from responseHeaders attribute w3c/webtransport#799, by @jan-ivar.
-
-
1 pull request merged.
-
Remove [SameObject] from responseHeaders attribute w3c/webtransport#799.
-
-
2 pull requests received 4 new comments.
-
Resolve datagram backpressure when sink queue has room w3c/webtransport#790 (3 comments by @jan-ivar, @saschanaz)
-
Error outgoing datagram writables on teardown instead of closing them w3c/webtransport#801 (1 comment by @jesup)
-
Lifecycle
-
1 charter started.
-
Chartered until 31 August 2028. Participants had to rejoin under this charter.
-
Past meetings
Participants
-
1 participant joined.
-
Filipi Da Silva Fuchter (Daily, Co) joined.
-
-
1 participant left.
-
Harald Alvestrand (Google LLC) left.
-
-
6 organizations joined.
-
Microsoft Corporation joined.
-
Daily, Co joined.
-
Akamai Technologies joined.
-
Apple Inc. joined.
-
Igalia joined.
-
Mozilla Foundation joined.
-
-
15 organizations left.
-
Jiangsu TPBlock Technology Co., Ltd. （江苏第三极区块链科技有限公司） left.
-
Datadog left.
-
Igalia left.
-
Shopify left.
-
Daily, Co left.
-
Cisco left.
-
Apple Inc. left.
-
Fraunhofer Gesellschaft left.
-
ByteDance left.
-
Intel Corporation left.
-
The New York Times left.
-
Microsoft Corporation left.
-
Mozilla Foundation left.
-
Akamai Technologies left.
-
Google LLC left.
-
GitHub
w3c/webtransport
-
7 issues opened.
-
How do atomic writes interact with the connection-level flow control? w3c/webtransport#798, by @vasilvv.
-
cleanup() closes outgoing datagram writables without checking WritableStreamCloseQueuedOrInFlight w3c/webtransport#797, by @jesup.
-
Link "TLS Keying Material Exporter" w3c/webtransport#794, by @otherdaniel.
-
"Concepts" section says that there are just two concepts w3c/webtransport#793, by @martinthomson.
-
Reference specific exporter constructions w3c/webtransport#791, by @martinthomson.
-
writeDatagrams only resolves back pressure once all buffered datagrams have been sent w3c/webtransport#787, by @jan-ivar.
-
-
1 issue closed.
-
Link "TLS Keying Material Exporter" w3c/webtransport#794.
-
-
5 issues received 8 new comments.
-
Support for reading http status code of WebTransport connect requests w3c/webtransport#777 (3 comments by @annevk, @jan-ivar)
-
How do atomic writes interact with the connection-level flow control? w3c/webtransport#798 (2 comments by @martinthomson, @vasilvv)
-
expose a TLS Keying Material Exporter / unique value for the TLS session w3c/webtransport#411 (1 comment by @Neustradamus)
-
writeDatagrams only resolves back pressure once all buffered datagrams have been sent w3c/webtransport#787 (1 comment by @jan-ivar)
-
-
5 pull requests opened.
-
Fix link for TLS Keying Material Exporter w3c/webtransport#796, by @jan-ivar.
-
Provide more complete pointers for exporters w3c/webtransport#792, by @martinthomson.
-
Resolve datagram backpressure when sink queue has room w3c/webtransport#790, by @jan-ivar.
-
Fix broken [[OutgoingDatagramsQueue]] refs w3c/webtransport#789, by @jan-ivar.
-
Fix highlighting of variables in algorithms, and use infra w3c/webtransport#788, by @jan-ivar.
-
-
7 pull requests merged.
-
Fix link for TLS Keying Material Exporter w3c/webtransport#796.
-
Fix broken [[OutgoingDatagramsQueue]] refs w3c/webtransport#789.
-
Fix highlighting of variables in algorithms, and use infra w3c/webtransport#788.
-
Wrap the exportKeyingMaterial definition w3c/webtransport#786.
-
Reword the notes on atomic writes w3c/webtransport#785.
-
Add clarifying prose and notes on datagram queues vs highWaterMark w3c/webtransport#784.
-
Fix echo sample client w3c/webtransport#782.
-
-
1 pull request reopened.
-
Resolve datagram backpressure when sink queue has room w3c/webtransport#790, by @jan-ivar.
-
-
2 pull requests received 13 new comments.
-
Resolve datagram backpressure when sink queue has room w3c/webtransport#790 (10 comments by @jan-ivar, @martinthomson, @nidhijaju)
-
Past meetings
GitHub
w3c/webtransport
-
1 issue opened.
-
Remove [SameObject] from responseHeaders w3c/webtransport#783, by @aran.
-
-
2 issues received 7 new comments.
-
Support for reading http status code of WebTransport connect requests w3c/webtransport#777 (6 comments by @annevk, @jan-ivar, @martinthomson, @petrroll)
-
-
4 pull requests opened.
-
Wrap the exportKeyingMaterial definition w3c/webtransport#786, by @martinthomson.
-
Reword the notes on atomic writes w3c/webtransport#785, by @martinthomson.
-
Add clarifying prose and notes on datagram queues vs highWaterMark w3c/webtransport#784, by @jan-ivar.
-
Fix echo sample client w3c/webtransport#782, by @jamesdavidson.
-
-
4 pull requests received 4 new comments.
Lifecycle
TR publications
-
2 documents published.
-
WebTransport published as a Candidate Recommendation Snapshot. History of WebTransport
-
WebTransport published as a Working Draft. History of WebTransport
-
Past meetings
GitHub
w3c/webtransport
-
5 issues opened.
-
WPT Interop 2026 scope w3c/webtransport#778, by @youennf.
-
Support for reading http status code of WebTransport connect requests w3c/webtransport#777, by @petrroll.
-
Deprecation notice for incomingHighWaterMark/outgoingHighWaterMark w3c/webtransport#776, by @Elchi3.
-
Unsatisfactory input validation of sendGroup option to createUni/Bi/Writable() w3c/webtransport#771, by @jan-ivar.
-
-
4 issues closed.
-
Deprecation notice for incomingHighWaterMark/outgoingHighWaterMark w3c/webtransport#776.
-
ExportKeyingMaterial should include a synchronous step that fails if we're failed/closed w3c/webtransport#768.
-
Unsatisfactory input validation of sendGroup option to createUni/Bi/Writable() w3c/webtransport#771.
-
-
5 issues received 17 new comments.
-
Support for reading http status code of WebTransport connect requests w3c/webtransport#777 (10 comments by @jan-ivar, @petrroll, @vasilvv, @wilaw)
-
exportKeyingMaterial: IDL marks context required, but the prose treats it as optional (and WebIDL then forces outputLength optional too) w3c/webtransport#774 (2 comments by @jan-ivar, @parrot6-hash)
-
ExportKeyingMaterial should include a synchronous step that fails if we're failed/closed w3c/webtransport#768 (2 comments by @jan-ivar)
-
Deprecation notice for incomingHighWaterMark/outgoingHighWaterMark w3c/webtransport#776 (1 comment by @jan-ivar)
-
-
7 pull requests opened.
-
More References update w3c/webtransport#781, by @ylafon.
-
Update references w3c/webtransport#780, by @ylafon.
-
Update references from RFC 8446 and RFC 8422 to RFC 9846 w3c/webtransport#779, by @wilaw.
-
Remove redundant optionality check for exportKeyingMaterial's context arg w3c/webtransport#775, by @jan-ivar.
-
Fix algorithms to highlight method arguments w3c/webtransport#773, by @jan-ivar.
-
Validate input w/TypeError ahead of state w3c/webtransport#772, by @jan-ivar.
-
Fix typo in exportKeyingMaterial steps w3c/webtransport#770, by @jan-ivar.
-
-
7 pull requests merged.
-
More References update w3c/webtransport#781.
-
Update references w3c/webtransport#780.
-
Update references from RFC 8446 and RFC 8422 to RFC 9846 w3c/webtransport#779.
-
Remove redundant optionality check for exportKeyingMaterial's context arg w3c/webtransport#775.
-
Validate input w/TypeError ahead of state w3c/webtransport#772.
-
Fix algorithms to highlight method arguments w3c/webtransport#773.
-
Fix issue #768 - return synchronously if closed/failed in ExportKeyingMaterial w3c/webtransport#769.
-
-
1 pull request closed.
-
Fix typo in exportKeyingMaterial steps w3c/webtransport#770.
-
-
4 pull requests received 7 new comments.
-
Fix issue #768 - return synchronously if closed/failed in ExportKeyingMaterial w3c/webtransport#769 (2 comments by @jan-ivar)
-
Remove redundant optionality check for exportKeyingMaterial's context arg w3c/webtransport#775 (1 comment by @jan-ivar)
TR publications
-
1 document published.
-
WebTransport published as a Working Draft. History of WebTransport
-
Past meetings
GitHub
w3c/webtransport
-
1 issue opened.
-
ExportKeyingMaterial should include a synchronous step that fails if we're failed/closed w3c/webtransport#768, by @jesup.
-
-
2 issues closed.
-
Pooling should require a strong secondKey in fetch's network partition key w3c/webtransport#760.
-
Pooled stats counters persist across session boundaries w3c/webtransport#762.
-
-
2 issues received 7 new comments.
-
Pooling should require a strong secondKey in fetch's network partition key w3c/webtransport#760 (4 comments by @jan-ivar, @martinthomson, @wilaw)
-
Pooled stats counters persist across session boundaries w3c/webtransport#762 (3 comments by @hardie, @jan-ivar, @pes10k)
-
-
5 pull requests opened.
-
Fix issue #768 - return synchronously if closed/failed in ExportKeyingMaterial w3c/webtransport#769, by @jesup.
-
Rename section to 'Server Authentication using Certificate Hashes' w3c/webtransport#767, by @wilaw.
-
Exclude counter-based stats from pooled connections w3c/webtransport#766, by @jan-ivar.
-
Fix references to fetch() and websocket w3c/webtransport#765, by @jan-ivar.
-
Gate pooling on a strong networkPartitionKey w3c/webtransport#764, by @jan-ivar.
-
-
3 pull requests merged.
-
Rename section to 'Server Authentication using Certificate Hashes' w3c/webtransport#767.
-
Exclude counter-based stats from pooled connections w3c/webtransport#766.
-
Fix references to fetch() and websocket w3c/webtransport#765.
-
-
1 pull request closed.
-
Gate pooling on a strong networkPartitionKey w3c/webtransport#764.
-
-
4 pull requests received 6 new comments.
-
Gate pooling on a strong networkPartitionKey w3c/webtransport#764 (3 comments by @jan-ivar, @martinthomson)
-
Fix issue #768 - return synchronously if closed/failed in ExportKeyingMaterial w3c/webtransport#769 (1 comment by @martinthomson)
-
Past meetings
GitHub
w3c/webtransport
-
4 issues opened.
-
Pooled stats counters persist across session boundaries w3c/webtransport#762, by @jan-ivar.
-
Should WT pool with non-WT requests? w3c/webtransport#761, by @jan-ivar.
-
Pooling should require a strong secondKey in fetch's network partition key w3c/webtransport#760, by @jan-ivar.
-
Can webtransport be used with cross origin isolation? w3c/webtransport#759, by @ValorZard.
-
-
4 issues closed.
-
Should WT pool with non-WT requests? w3c/webtransport#761.
-
Exporter API can't be implemented due to missing output length parameter. w3c/webtransport#756.
-
Can webtransport be used with cross origin isolation? w3c/webtransport#759.
-
-
5 issues received 13 new comments.
-
Should WT pool with non-WT requests? w3c/webtransport#761 (7 comments by @afrind, @jan-ivar, @LPardue, @martinthomson, @wilaw)
-
Node.js support for WebTransport w3c/webtransport#511 (3 comments by @kingdudely, @martenrichter, @wilaw)
-
Pooled stats counters persist across session boundaries w3c/webtransport#762 (1 comment by @jan-ivar)
-
-
2 pull requests opened.
-
Set up the WritableStreamDefaultWriter correctly. w3c/webtransport#763, by @jan-ivar.
-
Remove comparison to WebRTC in Privacy and Security section w3c/webtransport#758, by @jan-ivar.
-
-
3 pull requests merged.
-
Fix TLS exporter interface w3c/webtransport#757.
-
Remove comparison to WebRTC in Privacy and Security section w3c/webtransport#758.
-
Editorial: use "set up writer" algorithm w3c/webtransport#755.
-
-
1 pull request closed.
-
Set up the WritableStreamDefaultWriter correctly. w3c/webtransport#763.
-
-
3 pull requests received 4 new comments.
-
Remove comparison to WebRTC in Privacy and Security section w3c/webtransport#758 (2 comments by @jan-ivar, @martinthomson)
-
Past meetings
Participants
-
2 participants joined.
-
Nitin Dwivedi (Microsoft Corporation) joined.
-
Mayur patil (Microsoft Corporation) joined.
-
-
1 participant left.
-
SEUKYOON KANG (Gooroomee Inc.) left.
-
-
1 organization left.
-
Gooroomee Inc. left.
-
GitHub
w3c/webtransport
-
3 issues opened.
-
Exporter API can't be implemented due to missing output length parameter. w3c/webtransport#756, by @martinthomson.
-
Update wpt server to latest draft for interop w3c/webtransport#754, by @jan-ivar.
-
WebTransportWriter is still wrong and should not call SetUpWritableStreamDefaultWriter directly w3c/webtransport#753, by @saschanaz.
-
-
4 issues closed.
-
Test suite for user agents w3c/webtransport#622.
-
Support for CLOSE_FRAME w3c/webtransport#531.
-
Add an example showing receive side throttling w3c/webtransport#389.
-
Document that chunking boundaries aren't preserved in streams w3c/webtransport#189.
-
-
9 issues received 11 new comments.
-
WebTransportWriter is still wrong and should not call SetUpWritableStreamDefaultWriter directly w3c/webtransport#753 (3 comments by @jan-ivar, @MattiasBuelens)
-
Exporter API can't be implemented due to missing output length parameter. w3c/webtransport#756 (1 comment by @vasilvv)
-
Document that chunking boundaries aren't preserved in streams w3c/webtransport#189 (1 comment by @wilaw)
-
-
4 pull requests opened.
-
Fix TLS exporter interface w3c/webtransport#757, by @martinthomson.
-
Editorial: use "set up writer" algorithm w3c/webtransport#755, by @MattiasBuelens.
-
Update security questionnaire for clarity and accuracy w3c/webtransport#752, by @wilaw.
-
Update informative note w/SETTINGS_WT_ENABLED from draft 15 of ietf-webtrans-http3 w3c/webtransport#751, by @jan-ivar.
-
-
2 pull requests merged.
-
Update security questionnaire for clarity and accuracy w3c/webtransport#752.
-
Update informative note w/SETTINGS_WT_ENABLED from draft 15 of ietf-webtrans-http3 w3c/webtransport#751.
-
-
1 pull request received 1 new comment.
TR publications
-
2 documents published.
-
WebTransport published twice as a Working Draft. History of WebTransport
-
GitHub
w3c/webtransport
-
6 issues opened.
-
FAST checklist - March 2026 wide review w3c/webtransport#750, by @wilaw.
-
Zero-length buffers w3c/webtransport#747, by @gsnedders.
-
Generated HTML is invalid w3c/webtransport#742, by @ylafon.
-
Seek wide review ahead of Candidate Recommendation w3c/webtransport#741, by @wilaw.
-
The atomicWrite() algorithm appends to [[AtomicWriteRequests]] too late w3c/webtransport#739, by @jan-ivar.
-
-
8 issues closed.
-
Generated HTML is invalid w3c/webtransport#742.
-
Zero-length buffers w3c/webtransport#747.
-
wt.datagrams.outgoingHighWaterMark observable difference from streams spec w3c/webtransport#731.
-
The atomicWrite() algorithm appends to [[AtomicWriteRequests]] too late w3c/webtransport#739.
-
wt.datagrams.incomingHighWaterMark is a misnomer w3c/webtransport#723.
-
How would you prioritize the most recent frames/streams in WebTransport? w3c/webtransport#725.
-
-
6 issues received 10 new comments.
-
Make WebTransportError constructor compatible w3c/webtransport#715 (2 comments by @annevk, @jan-ivar)
-
7 pull requests opened.
-
Address errors in commit algorithm w3c/webtransport#749, by @martinthomson.
-
Streams are undifferentiated sequences of bytes w3c/webtransport#748, by @martinthomson.
-
Have WebTransportWriter use exported streams algorithms w3c/webtransport#746, by @jan-ivar.
-
Update api.csswg.org/bikeshed URLs to use spec-generator w3c/webtransport#745, by @kfranqueiro.
-
Remove duplicate send-order rules language w3c/webtransport#744, by @jan-ivar.
-
Fix atomicWrite() when the queue is empty w3c/webtransport#740, by @jan-ivar.
-
Expand on explainer.md with 2 more examples w3c/webtransport#738, by @jan-ivar.
-
-
10 pull requests merged.
-
Address errors in commit algorithm w3c/webtransport#749.
-
Streams are undifferentiated sequences of bytes w3c/webtransport#748.
-
Have WebTransportWriter use exported streams algorithms w3c/webtransport#746.
-
Update api.csswg.org/bikeshed URLs to use spec-generator w3c/webtransport#745.
-
Remove duplicate send-order rules language w3c/webtransport#744.
-
s/outgoingHighWaterMark/outgoingMaxBufferedDatagrams/ (and make it ulong) w3c/webtransport#737.
-
Fix atomicWrite() when the queue is empty w3c/webtransport#740.
-
s/incomingHighWaterMark/incomingMaxBufferedDatagrams/ (and make it ulong) w3c/webtransport#735.
-
Clarify null sendGroup w3c/webtransport#736.
-
Expand on explainer.md with 2 more examples w3c/webtransport#738.
-
-
2 pull requests received 2 new comments.
TR publications
-
1 document published.
-
WebTransport published as a Working Draft. History of WebTransport
-
Participants
-
1 participant left.
-
Caio Gondim (The New York Times) left.
-
GitHub
w3c/webtransport
-
7 issues opened.
-
wt.datagrams.outgoingHighWaterMark observable difference from streams spec w3c/webtransport#731, by @jan-ivar.
-
create{Bi|Uni}directionalStream() not specifying QuotaExceededError quota & requested members w3c/webtransport#730, by @jan-ivar.
-
[EnforceRange] usage is wrong w3c/webtransport#728, by @saschanaz.
-
Should exportKeyingMaterial return Uint8Array? w3c/webtransport#727, by @saschanaz.
-
WebTransportSendOptions should not make `sendGroup` as nullable with default value being null w3c/webtransport#726, by @saschanaz.
-
How would you prioritize the most recent frames/streams in WebTransport? w3c/webtransport#725, by @ValorZard.
-
wt.datagrams.incomingHighWaterMark is a misnomer w3c/webtransport#723, by @jan-ivar.
-
-
5 issues closed.
-
Should exportKeyingMaterial return Uint8Array? w3c/webtransport#727.
-
[EnforceRange] usage is wrong w3c/webtransport#728.
-
Do we want to allow web developers to add headers of the CONNECT request? w3c/webtransport#263.
-
atomicWrite clarification needed w3c/webtransport#714.
-
8 issues received 24 new comments.
-
How would you prioritize the most recent frames/streams in WebTransport? w3c/webtransport#725 (5 comments by @afrind, @ValorZard, @wilaw)
-
wt.datagrams.outgoingHighWaterMark observable difference from streams spec w3c/webtransport#731 (5 comments by @jan-ivar, @martinthomson)
-
Make WebTransportError constructor compatible w3c/webtransport#715 (4 comments by @jan-ivar, @wilaw)
-
WebTransportSendOptions should not make `sendGroup` as nullable with default value being null w3c/webtransport#726 (3 comments by @jan-ivar, @saschanaz)
-
wt.datagrams.incomingHighWaterMark is a misnomer w3c/webtransport#723 (2 comments by @jan-ivar, @martinthomson)
-
create{Bi|Uni}directionalStream() not specifying QuotaExceededError quota & requested members w3c/webtransport#730 (2 comments by @jan-ivar, @martinthomson)
-
-
10 pull requests opened.
-
s/outgoingHighWaterMark/outgoingMaxBufferedDatagrams/ (and make it ulong) w3c/webtransport#737, by @jan-ivar.
-
Clarify null sendGroup w3c/webtransport#736, by @wilaw.
-
s/incomingHighWaterMark/incomingMaxBufferedDatagrams/ (and make it ulong) w3c/webtransport#735, by @jan-ivar.
-
The quota exceeded error values can both be null w3c/webtransport#734, by @martinthomson.
-
Trailing whitespace is a plague w3c/webtransport#733, by @martinthomson.
-
Switch to Uint8Array for exportKeyingMaterial w3c/webtransport#732, by @martinthomson.
-
Use EnforceRange for the number type, not the attribute w3c/webtransport#729, by @saschanaz.
-
s/drained/starts draining/ w3c/webtransport#724, by @jan-ivar.
-
Update example to show calling abort + reorder send before receive examples w3c/webtransport#722, by @jan-ivar.
-
Combine step 3 and 4 in the process a WebTransport fetch response algo w3c/webtransport#721, by @jan-ivar.
-
-
9 pull requests merged.
-
The quota exceeded error values can both be null w3c/webtransport#734.
-
Switch to Uint8Array for exportKeyingMaterial w3c/webtransport#732.
-
Trailing whitespace is a plague w3c/webtransport#733.
-
Use EnforceRange for the number type, not the attribute w3c/webtransport#729.
-
s/drained/starts draining/ w3c/webtransport#724.
-
Add headers constructor option and readonly response wt.responseHeaders attribute w3c/webtransport#713.
-
Update example to show calling abort + reorder send before receive examples w3c/webtransport#722.
-
Modernize examples w3c/webtransport#720.
-
Combine step 3 and 4 in the process a WebTransport fetch response algo w3c/webtransport#721.
-
-
2 pull requests received 9 new comments.
-
Add headers constructor option and readonly response wt.responseHeaders attribute w3c/webtransport#713 (3 comments by @jan-ivar, @wilaw)
Lifecycle
-
1 charter extension.
-
Charter extended until 30 June 2026.
-
TR publications
-
1 document published.
-
WebTransport published as a Working Draft. History of WebTransport
-
Participants
-
1 participant left.
-
Jasper Hugo (Datadog) left.
-
GitHub
w3c/webtransport
-
3 issues opened.
-
Deep links to IETF WT Overview refer to outdated draft version numbers w3c/webtransport#718, by @wilaw.
-
Make WebTransportError constructor compatible w3c/webtransport#715, by @achristensen07.
-
atomicWrite clarification needed w3c/webtransport#714, by @jesup.
-
-
4 issues closed.
-
CSP policies for WebTransport? w3c/webtransport#59.
-
Deep links to IETF WT Overview refer to outdated draft version numbers w3c/webtransport#718.
-
Update explainer to cover recent features w3c/webtransport#694.
-
Reliable Reset is transport specific? w3c/webtransport#680.
-
-
4 issues received 10 new comments.
-
Make WebTransportError constructor compatible w3c/webtransport#715 (6 comments by @achristensen07, @jan-ivar)
-
-
4 pull requests opened.
-
Modernize examples w3c/webtransport#720, by @jan-ivar.
-
Update WebTransport references to draft-11 w3c/webtransport#719, by @wilaw.
-
Update WebTransport section links to latest draft w3c/webtransport#717, by @wilaw.
-
Updating explainer w3c/webtransport#716, by @wilaw.
-
-
4 pull requests merged.
-
Rely on request's WebTransport-hash list for CSP & cert verification w3c/webtransport#711.
-
Update WebTransport references to draft-11 w3c/webtransport#719.
-
Updating explainer w3c/webtransport#716.
-
Update WebTransport section links to latest draft w3c/webtransport#717.
-
-
4 pull requests received 18 new comments.
-
Add headers constructor option and readonly response wt.responseHeaders attribute w3c/webtransport#713 (4 comments by @jan-ivar, @martinthomson, @vasilvv)
-
Rely on request's WebTransport-hash list for CSP & cert verification w3c/webtransport#711 (1 comment by @jan-ivar)