Skip to content
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

Language for onnegotiationneeded is incomplete/inconsistent. #392

Closed
docfaraday opened this issue Nov 16, 2015 · 2 comments
Closed

Language for onnegotiationneeded is incomplete/inconsistent. #392

docfaraday opened this issue Nov 16, 2015 · 2 comments

Comments

@docfaraday
Copy link
Contributor

The language for onnegotiationneeded says the following should happen when a PC is marked "negotiation-needed" outside of stable:

"Otherwise, do nothing. If necessary, an event will be fired during setLocalDescription or setRemoteDescription processing, as described above."

However, the language for setRemoteDescription does not describe any action wrt negotiation-needed. I also cannot find any part of the spec that alludes to these two things interacting. I suspect the intent was to wait until a transition to stable (from either setLocal or setRemote) and fire the callback then.

@dontcallmedom
Copy link
Member

Step 3.2.9 of setting an RTCSessionDescription says:

if the negotiation-needed flag is set, the User Agent MUST queue a task to fire a simple event named negotiationneeded

@elagerway
Copy link
Contributor

Closing as per Dom's comments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants