-
Notifications
You must be signed in to change notification settings - Fork 2.7k
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
Clarify WebTransport BFCache interaction #9217
Conversation
Thanks a lot for the quick work here! Non-owner LGTM :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Generally looks good with minor editorial issues! I think WebTransport has other implementers involved too, right, so more than just Chrome can be said to be interested in this?
Web platform tests would also be good, ideally ones that show that WebTransport shutdown happens after WebSocket shutdown but before EventSource shutdown, since that's where you placed this.
Yes Mozilla is interested. |
I've updated the PR description with this information as well, but we have implementer interest from Mozilla now, and there are some WPTs at web-platform-tests/wpt#40117. Does this look good to you, @domenic? |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks great, thank you!
Based on w3c/webtransport#500 (comment), this PR explicitly calls the "context cleanup steps" in the WebTransport spec from within the HTML spec's "unloading document cleanup steps".
cc @rakina
(See WHATWG Working Mode: Changes for more details.)
/acknowledgements.html ( diff )
/document-lifecycle.html ( diff )
/infrastructure.html ( diff )
/references.html ( diff )