[webrtc-pc] iceConnectionState "checking" can happen without adding remote candidates (#2878)

fippo has just created a new issue for https://github.com/w3c/webrtc-pc:

== iceConnectionState "checking" can happen without adding remote candidates ==
The definition of the `checking` iceConnectionState
https://w3c.github.io/webrtc-pc/#rtcicetransportstate
is
> The [RTCIceTransport](https://w3c.github.io/webrtc-pc/#dom-rtcicetransport) has received at least one remote candidate and is checking candidate pairs and has either not yet found a connection or consent checks [[RFC7675](https://w3c.github.io/webrtc-pc/#bib-rfc7675)] have failed on all previously successful candidate pairs. In addition to checking, it may also still be gathering.

There is an edge-case in which "checking" can happen without remote candidates that is demonstrated by this fiddle:
https://jsfiddle.net/fippo/pnqtzfg1/7/
Checking can happen because a remote prflx candidate learned from incoming STUN binding requests is used to create a pair.

Solution:
🍎 remove "has received at least one remote candidate"
🍐 changed "has received" to "has received or discovered"

Please view or discuss this issue at https://github.com/w3c/webrtc-pc/issues/2878 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Monday, 12 June 2023 08:54:32 UTC