-
Notifications
You must be signed in to change notification settings - Fork 18
Use RTCIceCandidatePair interface in RTCIceTransport #205
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
Open
sam-vi
wants to merge
6
commits into
w3c:main
Choose a base branch
from
sam-vi:2930-candidatepair-interface
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
Show all changes
6 commits
Select commit
Hold shift + click to select a range
7c3a703
Use RTCIceCandidatePair interface in RTCIceTransport.
sam-vi 83d5a3c
Compare RTCIceCandidatePair identity instead of match algo.
sam-vi cd26c2a
Modify the change of selected pair algo in RTCIceTransport.
sam-vi 56a6071
Fix markup typo (unrelated to this PR)
dontcallmedom ca19e02
Merge branch 'w3c:main' into 2930-candidatepair-interface
sam-vi 469ff70
Qualify the CandidatePairs slot with the associated transport.
sam-vi File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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.
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.
Was this change discussed?
It looks ok to me but this reduces the ability of creating event to candidate pairs created by the UA
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.
This is in line with the goals of w3c/webrtc-pc#2930, namely restricting JS's ability to create invalid pairs and simplifying validation steps in specs. It reduces the burden of validation in the
RTCIceTransport
extension API specs, and provides web developers with a loose guarantee that events will signal candidate pairs that can be provided as inputs to otherRTCIceTransport
methods (barring state errors).I hadn't considered this particular change to be especially significant, but we could discuss in the next interim if needed.
My thoughts are:
RTCIceCandidatePairEventInit
to valid candidate pairs created by the UA.RTCPeerConnectionIceErrorEvent
) that is used in that limited scope.RTCIceCandidatePair
.