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

Invalidate [[LastReturnedParameters]] in RTCRtpSender.setParameters #1868

Merged
merged 1 commit into from
May 3, 2018

Conversation

Orphis
Copy link
Contributor

@Orphis Orphis commented May 2, 2018

This prevents sequences of getParameters() and then
multiple setParameters() call.

Fixes #1857

@fippo
Copy link
Contributor

fippo commented May 2, 2018

I think you need to update

If sender's [[LastReturnedParameters]] internal slot is empty, meaning getParameters 
has never been called, return a promise rejected with a newly created InvalidStateError.

too. It might now have been called before even when this is set to null.

Copy link
Contributor

@fippo fippo left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM with minor suggestion

This prevents sequences of getParameters() and then
multiple setParameters() call.

Fixes w3c#1857
@Orphis Orphis force-pushed the invalidate_lastreturnedparameters branch from bd639d9 to 9bee9f5 Compare May 3, 2018 11:33
@aboba aboba merged commit 758c94c into w3c:master May 3, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants