-
Notifications
You must be signed in to change notification settings - Fork 452
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Tracking - WebTransport browser bugs #2572
Labels
kind/tracking
A meta-issue for tracking work
Comments
achingbrain
added
need/triage
Needs initial labeling and prioritization
kind/tracking
A meta-issue for tracking work
and removed
need/triage
Needs initial labeling and prioritization
labels
Jun 3, 2024
5 tasks
11 tasks
3 tasks
achingbrain
pushed a commit
to ipfs/helia
that referenced
this issue
Nov 18, 2024
WebTransport is still not working reliably across different browsers. Moreover, the go-libp2p implementation needs to be updated to meet newer revisions of the spec. As we discussed during Helia WG, the most sensible thing for now is to remove WebTransport from the default transports. Refs libp2p/js-libp2p#2572 --------- Co-authored-by: Daniel N <[email protected]>
Another issue that should be monitor is probably this one https://bugzilla.mozilla.org/show_bug.cgi?id=1659672 even though I'm not 100% sure it is what is blocking e2e test on firefox |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
A list of browser bugs that block use of WebTransport.
Chrome/Chromium
Firefox
Safari/WebKit
WebTransport has been implemented and shipped behind a feature flag.
They have implemented the latest version of the spec which is incompatible with other shipping versions.
Edge
WebTransport has been implemented and shipped. Needs to be verified that it works as expected.
The text was updated successfully, but these errors were encountered: