-
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
offerToReceive: Rewrite to handle two options to createOffer #1686
Conversation
Better looking diff (--patience): https://dpaste.de/heHB |
@fippo, sorry that this breaks some of your PRs, but it should address the problem you brought up with two options at the same time. |
webrtc.html
Outdated
"#dom-rtcpeerconnection-createoffer">createOffer</a> steps:</p> | ||
<ol> | ||
<li> | ||
<p>Let <var>options</var> be the methods second argument.</p> |
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.
first argument? (I am glad we're dealing with the legacy callbacks elsewhere)
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.
Will fix!
no worries, I expected that i'll have to update my PRs. This looks pretty good, I was afraid it would be more ugly! |
I've added an intro text and a short description of the attributes. Can you take a look @fippo Readable diff: https://dpaste.de/0jb8 |
Extended test to use two options: web-platform-tests/wpt#8450 |
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.
OK
spec change in w3c/webrtc-pc#1686
I think this is cleaner. Question is if we want to have a description of the individual options.