-
Notifications
You must be signed in to change notification settings - Fork 115
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
Queue two tasks upon finishing ICE gathering, and fire gatheringstatechange & icegatheringstatechange in same task #2894
Conversation
…ecandidate events in same task.
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.
This looks good to me.
The general principle of state-setting seems to be that we change the state before we fire the event that informs the user of the state change; the old code violated this, so was clearly wrong.
I think we might be missing the steps that add an a=end-of-candidates to the local description. |
Also, it looks like we'll fire duplicate null candidates here. We should only fire the null candidate if the RTCPeerConnection.iceGatheringState just transitioned to "complete". |
Isn't that covered by JSEP? This spec generally doesn't get into that. In any case that seems like a separate issue. |
Hmm. So JSEP handles this when creating a new local description, but does not update the existing local description. Maybe we shouldn't be updating? Anyhow, yeah, separate issue. |
Ah, I forgot to remove the now unused "update the ICE gathering state" algorithm. Thanks for catching that! |
Seems good to merge. Needs test. |
WPT tests were merged in web-platform-tests/wpt#44687 (two tests). https://wpt.fyi/results/webrtc/RTCPeerConnection-iceGatheringState.html |
Hi @dontcallmedom I'm getting this error. It says to see developer console, where can I see that? Trying to figure out how to bother you less ;)
Also the next step "Check amendment annotations on substantive changes to Rec / check-amendment (pull_reques" seems to have passed, which seems odd if it failed on amendments. |
The way I check it is by running the ReSpec document in my local browser (served via a local http server since otherwise you'd hit CORS issues). The error in the developer console says:
The problem here is that you're applying the change to the whole "rtcicetransport" section, which contains already a place with another change; I think the solution would probably to add a I'm happy to leave it to you, or do it on my end as you prefer.
That job's role is only to check that a non-editorial PR is listed in amendments; let me know if you see a better name to use for the check. |
Fixes #2892.
Fixes #2893.
Fixes #2896.
cc @docfaraday
Preview | Diff