Fix Chrome support for RTCPeerConnection parameters#25697
Merged
Conversation
Elchi3
requested changes
Jan 17, 2025
Member
Elchi3
left a comment
There was a problem hiding this comment.
See the build failure, some sub features are earlier than the parent now and that doesn't work.
Elchi3
approved these changes
Jan 20, 2025
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Summary
Fixes Chrome support data for the following
RTCPeerConnectionparameters:iceCandidatePoolSizeiceServersiceTransportPolicy(akaiceTransports)Test results and supporting details
See #16595 (comment) for the evidence.
Related issues
Fixes #16595.