You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
At the moment, one is supposed to figure out whether a candidate is local or remote based on its position in a candidate pair.
This doesn't cover the case where you have candidates that aren't paired with anything - for instance IPv6 local candidates when talking to an IPv4-only remote system.
There should be an "isRemote = false" field on RTCIceCandidateStats, just like we have on RTCRTPStreamStats.
The text was updated successfully, but these errors were encountered:
I was wrong. Local candidates have their "type" field set to "local-candidate", while remote candidates have their "type" field set to "remote-candidate", so they're actually distinguishable. Closing issue.
At the moment, one is supposed to figure out whether a candidate is local or remote based on its position in a candidate pair.
This doesn't cover the case where you have candidates that aren't paired with anything - for instance IPv6 local candidates when talking to an IPv4-only remote system.
There should be an "isRemote = false" field on RTCIceCandidateStats, just like we have on RTCRTPStreamStats.
The text was updated successfully, but these errors were encountered: