-
Notifications
You must be signed in to change notification settings - Fork 3k
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
Add RTCPeerConnection-close.html tests from PR13499 #16045
base: master
Are you sure you want to change the base?
Add RTCPeerConnection-close.html tests from PR13499 #16045
Conversation
PR not to be merged yet. |
The mix with negotiated makes sense because negotiated data channels that don't have a matching end on the remote side behave differently - they are I guess they could be moved into separate tests. Edit: It doesn't need to be 24 channels. Two should do. (Background: I think this was originally part of the ID tests.) |
OK, it makes sense to me to make a very simple test checking closure of a given pc and state of its channels. And add other tests for negotiated channels. Also, while the data channels of the pc being closed should get their state synchronously changed, this is probably asynchronously done for the channels of the other pc. |
👌
Good catch.
Not sure I can follow you. If you mean "All local channels should be closed immediately" and this is what we should test for, then, yes, I would agree. |
Does this still apply? If yes, please add "do not merge yet" label and explain what the next step is. Thanks! |
No description provided.