Update notes regarding default value of an RTCPeerConnection option #12301
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
github-actions
bot
added
the
data:api 🐇
queengooborg
added a commit
to queengooborg/browser-compat-data
that referenced
this pull request
Sep 8, 2021
|
@ddbeck I believe you have fairly strong opinions on the wording of notes like this? |
ddbeck
reviewed
Sep 14, 2021
jpmedley
approved these changes
Sep 21, 2021
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Cherry-picked from #12300. This PR updates the notes regarding the default value of
rtcpMuxPolicyfor Chrome when creating a new instance and indicates what the new default value is. Currently, the notes don't mention what the new default value is, which is slightly unhelpful. (There's only two values available, but this note update removes the need to scroll up on the page and find that out.)