Correct data for the RTCPeerConnection API#12300
Conversation
foolip
left a comment
There was a problem hiding this comment.
Descriptions for all returns_promise entries need updating.
foolip
left a comment
There was a problem hiding this comment.
A big PR, unfortunately it's easy to find more things wrong with the data on each pass. However, I promise that with this round, if I find even more next time, I'll file follow-up issues for the rest instead.
foolip
left a comment
There was a problem hiding this comment.
I've reviewed everything again and can't spot any more issues. Thanks for sorting out this huge mess, this is much, much better now! 🥳
|
@ddbeck I think the new subfeatures for promises are release note worthy. |
|
@foolip Good idea. In the forthcoming release notes, I've included this with the text for #11630. If you want to review today before the release, that would be helpful (but not required). |
* Bump version to v4.0.5 * Bump known issues * Add release note for #12417 * Add release note for #12454 * Add release note for #12417 * Add release note for #12346 * Add release note for #12455 * Add release note for #12518 * Add release note for #11630 * Add release note for #12300 * Add release note for #12552 * Add release stats * Add release date * Fix a typo
|
@ddbeck I've reviewed the release notes after the fact, looks good, thank you! |
This PR corrects the data throughout the RTCPeerConnection API, which was a big mess, mostly due to copy-paste error. The fixes include the following:
Add data regarding the prefixed constructorThis one was done in Represent support for webkitRTCPeerConnection #12196 already, though the non-prefixed version number was a little off based on my testing, so this is a quick correction.Updates the notes regarding the defaultCherry-picked in Update notes regarding default value of an RTCPeerConnection option #12301.rtcpMuxPolicyvalue in Chrome when constructing a new instance. The notes didn't mention what the new default value is, which is slightly unhelpful. (There's only two values available, but the note update removes the need to scroll up on the page and find that out.)createDataChannelbased upon results from the mdn-bcd-collector project (v3.3.0).truefor many of the features, however since we have ranged values, we're able to replace thetruewith≤37for WebView, and mirror Chrome straight to Chrome Android since we know Chrome Android has supported this API back then.There's a lot of changes made in this PR, so I would love to get it reviewed and merged ASAP!