-
Notifications
You must be signed in to change notification settings - Fork 114
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
Don't fire connectionstatechange on pc.close(). #2876
Conversation
I'm getting validation errors, but I don't see anything wrong. @dontcallmedom am I using the append amendments type wrong?
|
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.
I don't think this is a change of behaviour.
Close is probably setting the connection state to closed synchronously.
Then the algorithm will try to update and be a no-op.
Worth clarifying though
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.
I don't understand the markup, but agree with the behavior change (which I think is probably the current behavior of browsers; test needed), so marking myself as approving.
object associated with the {{RTCDtlsTransport}} object whose state changed. | ||
</p> | ||
</li> | ||
<li class="add-to-connectionstate-algo"> |
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.
Is this a proper use of the "class" attribute?
I've fixed the markup issue in 46a3411 - the "append" treatment needed to be handled on the |
Fixes #2865.
Preview | Diff