diff --git a/webrtc.html b/webrtc.html index a6f82b4d6..9515813a2 100644 --- a/webrtc.html +++ b/webrtc.html @@ -254,7 +254,7 @@

RTCIceCredentialType Enum

enum RTCIceCredentialType {
-  "password",
+  "password"
 };
@@ -300,12 +300,12 @@

Dictionary {{RTCIceServer}} Members

If this {{RTCIceServer}} object represents a TURN server, and credentialType is - "password", then this attribute specifies the + {{RTCIceCredentialType/"password"}}, then this attribute specifies the username to use with that TURN server.

credentialType of type {{RTCIceCredentialType}}, defaulting to - "password"
+ {{RTCIceCredentialType/"password"}}

If this {{RTCIceServer}} object represents a TURN server, then this attribute specifies how @@ -545,24 +545,24 @@

RTCSignalingState Enum

- - - - @@ -585,19 +585,19 @@

RTCSignalingState Enum

Caller transition:
Callee transition:
@@ -620,20 +620,20 @@

RTCIceGatheringState Enum

+ {{RTCIceGathererState/"gathering"}} state. + {{RTCIceGathererState/"complete"}} gathering state.
have-local-offerA local description, of type "offer", has been successfully + A local description, of type {{RTCSdpType/"offer"}}, has been successfully applied.
have-remote-offerA remote description, of type "offer", has been + A remote description, of type {{RTCSdpType/"offer"}}, has been successfully applied.
have-local-pranswerA remote description of type "offer" has been successfully - applied and a local description of type "pranswer" has been + A remote description of type {{RTCSdpType/"offer"}} has been successfully + applied and a local description of type {{RTCSdpType/"pranswer"}} has been successfully applied.
have-remote-pranswerA local description of type "offer" has been successfully - applied and a remote description of type "pranswer" has been + A local description of type {{RTCSdpType/"offer"}} has been successfully + applied and a remote description of type {{RTCSdpType/"pranswer"}} has been successfully applied.
new Any of the {{RTCIceTransport}}s are in the - "new" gathering state and none of the transports are - in the "gathering" state, or there are no + {{RTCIceGathererState/"new"}} gathering state and none of the transports are + in the {{RTCIceGathererState/"gathering"}} state, or there are no transports.
gathering Any of the {{RTCIceTransport}}s are in the - "gathering" state.
complete At least one {{RTCIceTransport}} exists, and all {{RTCIceTransport}}s are in the - "completed" gathering state.
@@ -735,39 +735,39 @@

RTCIceConnectionState Enum

failed The previous state doesn't apply and any {{RTCIceTransport}}s are in the - "failed" state. + {{RTCIceTransportState/"failed"}} state. disconnected None of the previous states apply and any {{RTCIceTransport}}s are in the - "disconnected" state. + {{RTCIceTransportState/"disconnected"}} state. new None of the previous states apply and all {{RTCIceTransport}}s are in the - "new" or "closed" state, + {{RTCIceTransportState/"new"}} or {{RTCIceTransportState/"closed"}} state, or there are no transports. checking None of the previous states apply and any {{RTCIceTransport}}s are in the - "new" or "checking" state. + {{RTCIceTransportState/"new"}} or {{RTCIceTransportState/"checking"}} state. completed None of the previous states apply and all {{RTCIceTransport}}s are in the - "completed" or "closed" state. + {{RTCIceTransportState/"completed"}} or {{RTCIceTransportState/"closed"}} state. connected None of the previous states apply and all {{RTCIceTransport}}s are in the - "connected", "completed" or - "closed" state. + {{RTCIceTransportState/"connected"}}, {{RTCIceTransportState/"completed"}} or + {{RTCIceTransportState/"closed"}} state. @@ -882,15 +882,15 @@

Constructor

  • If the value of configuration.{{RTCConfiguration/iceTransportPolicy}} is - undefined, set it to "all".

    + undefined, set it to {{RTCIceTransportPolicy/"all"}}.

  • If the value of configuration.{{RTCConfiguration/bundlePolicy}} is - undefined, set it to "balanced".

    + undefined, set it to {{RTCBundlePolicy/"balanced"}}.

  • If the value of configuration.{{RTCConfiguration/rtcpMuxPolicy}} is - undefined, set it to "require".

    + undefined, set it to {{RTCRtcpMuxPolicy/"require"}}.

  • Let connection have a [[\Configuration]] @@ -928,19 +928,19 @@

    Constructor

  • Set connection's [= signaling state =] to - "stable".

    + {{RTCSignalingState/"stable"}}.

  • Set connection's [= ICE connection state =] to - "new".

    + {{RTCIceConnectionState/"new"}}.

  • Set connection's [= ICE gathering state =] to - "new".

    + {{RTCIceGatheringState/"new"}}.

  • Set connection's [= connection state =] to - "new".

    + {{RTCPeerConnectionState/"new"}}.

  • Let connection have a @@ -1116,7 +1116,7 @@

    Update the ICE gathering state

    connection.

  • -

    If newState is "completed", +

    If newState is {{RTCIceGatheringState/"complete"}}, [= fire an event =] named {{icecandidate}} using the {{RTCPeerConnectionIceEvent}} interface with the candidate attribute set to @@ -1149,9 +1149,9 @@

    Set the RTCSessionDescription

    1. If description.type is - "rollback" and connection's [= signaling state =] is either - "stable", "have-local-pranswer", or - "have-remote-pranswer", then [= reject =] p + {{RTCSdpType/"rollback"}} and connection's [= signaling state =] is either + {{RTCSignalingState/"stable"}}, {{RTCSignalingState/"have-local-pranswer"}}, or + {{RTCSignalingState/"have-remote-pranswer"}}, then [= reject =] p with a newly [= exception/create | created =] {{InvalidStateError}} and abort these steps.

    2. @@ -1234,9 +1234,9 @@

      Set the RTCSessionDescription

      true, then abort these steps.

    3. -

      If description is of type "offer" +

      If description is of type {{RTCSdpType/"offer"}} and the [= signaling state =] of connection is - "stable" then for each transceiver + {{RTCSignalingState/"stable"}} then for each transceiver in connection's [= set of transceivers =], run the following steps:

        @@ -1264,17 +1264,17 @@

        Set the RTCSessionDescription

        1. -

          If description is of type "offer", set +

          If description is of type {{RTCSdpType/"offer"}}, set connection.[[\PendingLocalDescription]] to a new {{RTCSessionDescription}} object constructed from description, set - connection's [= signaling state =] to "have-local-offer", + connection's [= signaling state =] to {{RTCSignalingState/"have-local-offer"}}, and [= release early candidates =].

        2. -

          If description is of type "answer", then +

          If description is of type {{RTCSdpType/"answer"}}, then this completes an offer answer negotiation. Set connection.[[\CurrentLocalDescription]] to a new {{RTCSessionDescription}} object @@ -1287,7 +1287,7 @@

          Set the RTCSessionDescription

          connection.[[\LastCreatedOffer]] and connection.[[\LastCreatedAnswer]] to "", set connection's - [= signaling state =] to "stable", and + [= signaling state =] to {{RTCSignalingState/"stable"}}, and [= release early candidates =]. Finally, if none of the ICE credentials in connection.[[\LocalIceCredentialsToReplace]] are @@ -1297,11 +1297,11 @@

          Set the RTCSessionDescription

        3. -

          If description is of type "pranswer", +

          If description is of type {{RTCSdpType/"pranswer"}}, then set connection.[[\PendingLocalDescription]] to a new {{RTCSessionDescription}} object constructed from description, set connection's - [= signaling state =] to "have-local-pranswer", + [= signaling state =] to {{RTCSignalingState/"have-local-pranswer"}}, and [= release early candidates =].

        @@ -1312,16 +1312,16 @@

        Set the RTCSessionDescription

        1. -

          If description is of type "offer", set +

          If description is of type {{RTCSdpType/"offer"}}, set connection.[[\PendingRemoteDescription]] attribute to a new {{RTCSessionDescription}} object constructed from description, and set connection's - [= signaling state =] to "have-remote-offer".

          + [= signaling state =] to {{RTCSignalingState/"have-remote-offer"}}.

        2. -

          If description is of type "answer", then +

          If description is of type {{RTCSdpType/"answer"}}, then this completes an offer answer negotiation. Set connection.[[\CurrentRemoteDescription]] to a new {{RTCSessionDescription}} object @@ -1334,7 +1334,7 @@

          Set the RTCSessionDescription

          connection.[[\LastCreatedOffer]] and connection.[[\LastCreatedAnswer]] to "", and set connection's - [= signaling state =] to "stable". + [= signaling state =] to {{RTCSignalingState/"stable"}}. Finally, if none of the ICE credentials in connection.[[\LocalIceCredentialsToReplace]] are present in the newly set @@ -1344,16 +1344,16 @@

          Set the RTCSessionDescription

        3. -

          If description is of type "pranswer", +

          If description is of type {{RTCSdpType/"pranswer"}}, then set connection.[[\PendingRemoteDescription]] to a new {{RTCSessionDescription}} object constructed from description and set connection's - [= signaling state =] to "have-remote-pranswer".

          + [= signaling state =] to {{RTCSignalingState/"have-remote-pranswer"}}.

      1. -

        If description is of type "answer", and it +

        If description is of type {{RTCSdpType/"answer"}}, and it initiates the closure of an existing SCTP association, as defined in [[!SCTP-SDP]], Sections 10.3 and 10.4, set the value of connection.[[\SctpTransport]] to @@ -1365,15 +1365,15 @@

        Set the RTCSessionDescription

        errorList be empty lists.

      2. -

        If description is of type "answer" or - "pranswer", then run the following steps:

        +

        If description is of type {{RTCSdpType/"answer"}} or + {{RTCSdpType/"pranswer"}}, then run the following steps:

        1. If description initiates the establishment of a new SCTP association, as defined in [[!SCTP-SDP]], Sections 10.3 and 10.4, [= create an RTCSctpTransport =] with an initial state of - "connecting" and assign the result to the + {{RTCSctpTransportState/"connecting"}} and assign the result to the [[\SctpTransport]] slot. Otherwise, if an SCTP association is established, but the "max-message-size" SDP attribute is updated, @@ -1393,7 +1393,7 @@

          Set the RTCSessionDescription

          according to [[!RTCWEB-DATA-PROTOCOL]]. If no available ID could be generated, set channel.[[\ReadyState]] to - "closed", and add channnel + {{RTCDataChannelState/"closed"}}, and add channnel to errorList.
        @@ -1406,7 +1406,7 @@

        Set the RTCSessionDescription

        lists.

      3. -

        If description is not of type "rollback", then +

        If description is not of type {{RTCSdpType/"rollback"}}, then run the following steps:

        1. @@ -1481,8 +1481,8 @@

          Set the RTCSessionDescription

          description =].

        2. -

          If direction is "sendrecv" or - "recvonly", +

          If direction is {{RTCRtpTransceiverDirection/"sendrecv"}} or + {{RTCRtpTransceiverDirection/"recvonly"}}, set transceiver.[[\Receptive]] to true, otherwise set it to false.

        3. @@ -1494,14 +1494,14 @@

          Set the RTCSessionDescription

          agent is currently prepared to receive.

          If the direction is - "sendonly" or "inactive", + {{RTCRtpTransceiverDirection/"sendonly"}} or {{RTCRtpTransceiverDirection/"inactive"}}, the receiver is not prepared to receive anything, and the list will be empty.

        4. If description is of type - "answer" or "pranswer", + {{RTCSdpType/"answer"}} or {{RTCSdpType/"pranswer"}}, then run the following steps:

          1. @@ -1515,9 +1515,9 @@

            Set the RTCSessionDescription

          2. If direction is - "sendonly" or "inactive", + {{RTCRtpTransceiverDirection/"sendonly"}} or {{RTCRtpTransceiverDirection/"inactive"}}, and transceiver.[[\FiredDirection]] is either - "sendrecv" or "recvonly", + {{RTCRtpTransceiverDirection/"sendrecv"}} or {{RTCRtpTransceiverDirection/"recvonly"}}, then run the following steps:

            1. @@ -1549,7 +1549,7 @@

              Set the RTCSessionDescription

              in description:

              1. -

                If the description is of type "offer" +

                If the description is of type {{RTCSdpType/"offer"}} and contains a request to receive simulcast, use the order of the rid values specified in the simulcast attribute to create an {{RTCRtpEncodingParameters}} dictionary for @@ -1597,7 +1597,7 @@

                Set the RTCSessionDescription

                [= Create an RTCRtpTransceiver =] with sender, receiver and an {{RTCRtpTransceiverDirection}} - value of "recvonly", and let + value of {{RTCRtpTransceiverDirection/"recvonly"}}, and let transceiver be the result.

              2. @@ -1609,8 +1609,8 @@

                Set the RTCSessionDescription

            2. -

              If description is of type "answer" - or "pranswer", and transceiver. +

              If description is of type {{RTCSdpType/"answer"}} + or {{RTCSdpType/"pranswer"}}, and transceiver. [[\Sender]].[[\SendEncodings]] .length is greater than 1, then run the following steps:

                @@ -1650,12 +1650,12 @@

                Set the RTCSessionDescription

                description =], but with the send and receive directions reversed to represent this peer's point of view. If the [= media description =] is rejected, - set direction to "inactive". + set direction to {{RTCRtpTransceiverDirection/"inactive"}}.

              1. -

                If direction is "sendrecv" - or "recvonly", let msids be a +

                If direction is {{RTCRtpTransceiverDirection/"sendrecv"}} + or {{RTCRtpTransceiverDirection/"recvonly"}}, let msids be a list of the MSIDs that the media description indicates transceiver.[[\Receiver]].[[\ReceiverTrack]] is to be associated with. Otherwise, let @@ -1679,7 +1679,7 @@

                Set the RTCSessionDescription

              2. If description is of type - "answer" or "pranswer", then run + {{RTCSdpType/"answer"}} or {{RTCSdpType/"pranswer"}}, then run the following steps:

                1. @@ -1744,7 +1744,7 @@

                  Set the RTCSessionDescription

              3. -

                Otherwise, (if description is of type "rollback") +

                Otherwise, (if description is of type {{RTCSdpType/"rollback"}}) run the following steps:

                1. @@ -1774,7 +1774,7 @@

                  Set the RTCSessionDescription

                2. If the signaling state of connection - is "have-remote-offer", run the following + is {{RTCSignalingState/"have-remote-offer"}}, run the following sub steps:

                  1. @@ -1805,12 +1805,12 @@

                    Set the RTCSessionDescription

                    Set connection.[[\PendingLocalDescription]] and connection.[[\PendingRemoteDescription]] to null, and set connection's - [= signaling state =] to "stable".

                    + [= signaling state =] to {{RTCSignalingState/"stable"}}.

                3. -

                  If description is of type "answer", then run +

                  If description is of type {{RTCSdpType/"answer"}}, then run the following steps:

                  1. @@ -1832,7 +1832,7 @@

                    Set the RTCSessionDescription

                  2. If connection's [= signaling state =] is now - "stable", [= update the negotiation-needed + {{RTCSignalingState/"stable"}}, [= update the negotiation-needed flag =]. If connection.[[\NegotiationNeeded]] was true both before and after this update,

                    [= Chain =] a step to @@ -2046,7 +2046,7 @@

                    Set the configuration

                    If scheme name is turn or turns, and server.credentialType is - "password", and + {{RTCIceCredentialType/"password"}}, and server.credential is not a DOMString, then [= exception/throw =] an {{InvalidAccessError}}.

                    @@ -2392,8 +2392,8 @@

                    Methods

                    1. If connection's [= signaling state =] is - neither "stable" nor - "have-local-offer", return a promise + neither {{RTCSignalingState/"stable"}} nor + {{RTCSignalingState/"have-local-offer"}}, return a promise [= rejected =] with a newly [= exception/create | created =] {{InvalidStateError}}.

                    2. @@ -2484,20 +2484,20 @@

                      Methods

                      1. If the {{RTCRtpTransceiver/direction}} is - "sendrecv", exclude any codecs not + {{RTCRtpTransceiverDirection/"sendrecv"}}, exclude any codecs not included in the intersection of RTCRtpSender.getCapabilities(kind).codecs and RTCRtpReceiver.getCapabilities(kind).codecs.

                      2. If the {{RTCRtpTransceiver/direction}} is - "sendonly", exclude any codecs not + {{RTCRtpTransceiverDirection/"sendonly"}}, exclude any codecs not included in RTCRtpSender.getCapabilities(kind).codecs.

                      3. If the {{RTCRtpTransceiver/direction}} is - "recvonly", exclude any codecs not + {{RTCRtpTransceiverDirection/"recvonly"}}, exclude any codecs not included in RTCRtpReceiver.getCapabilities(kind).codecs.

                      4. @@ -2532,7 +2532,7 @@

                        Methods

                        Let offer be a newly created {{RTCSessionDescriptionInit}} dictionary with its type member initialized to the string - "offer" and its sdp member + {{RTCSdpType/"offer"}} and its sdp member initialized to sdpString.

                      5. Set the [[\LastCreatedOffer]] internal slot to @@ -2581,7 +2581,7 @@

                        Methods

                        An answer can be marked as provisional, as described in [[!JSEP]], by setting the {{RTCSessionDescription/type}} to - "pranswer".

                        + {{RTCSdpType/"pranswer"}}.

                        When the method is called, the user agent MUST run the following steps:

                          @@ -2610,8 +2610,8 @@

                          Methods

                          RTCPeerConnection-setLocalDescription-answer.html, RTCPeerConnection-setLocalDescription-pranswer.html">

                          If connection's [= signaling state =] - is neither "have-remote-offer" nor - "have-local-pranswer", return a promise + is neither {{RTCSignalingState/"have-remote-offer"}} nor + {{RTCSignalingState/"have-local-pranswer"}}, return a promise [= rejected =] with a newly [= exception/create | created =] {{InvalidStateError}}.

                          @@ -2671,9 +2671,9 @@

                          Methods

                          This may be necessary if, for example, createAnswer was called when an {{RTCRtpTransceiver}}'s direction was - "recvonly", but while performing the + {{RTCRtpTransceiverDirection/"recvonly"}}, but while performing the [= in-parallel steps to create an answer =], the - direction was changed to "sendrecv", + direction was changed to {{RTCRtpTransceiverDirection/"sendrecv"}}, requiring additional inspection of video encoding resources.
  • @@ -2694,20 +2694,20 @@

    Methods

    1. If the {{RTCRtpTransceiver/direction}} is - "sendrecv", exclude any codecs not + {{RTCRtpTransceiverDirection/"sendrecv"}}, exclude any codecs not included in the intersection of RTCRtpSender.getCapabilities(kind).codecs and RTCRtpReceiver.getCapabilities(kind).codecs.

    2. If the {{RTCRtpTransceiver/direction}} is - "sendonly", exclude any codecs not + {{RTCRtpTransceiverDirection/"sendonly"}}, exclude any codecs not included in RTCRtpSender.getCapabilities(kind).codecs.

    3. If the {{RTCRtpTransceiver/direction}} is - "recvonly", exclude any codecs not + {{RTCRtpTransceiverDirection/"recvonly"}}, exclude any codecs not included in RTCRtpReceiver.getCapabilities(kind).codecs.

    4. @@ -2734,7 +2734,7 @@

      Methods

      Let answer be a newly created {{RTCSessionDescriptionInit}} dictionary with its type member initialized to the string - "answer" and its sdp member + {{RTCSdpType/"answer"}} and its sdp member initialized to sdpString.

    5. Set the [[\LastCreatedAnswer]] internal slot to @@ -2792,14 +2792,14 @@

      Methods

    6. Let type be description.type if present, or - "offer" if not present and + {{RTCSdpType/"offer"}} if not present and connection's [= signaling state =] is either - "stable", "have-local-offer", - or "have-remote-pranswer"; otherwise - "answer".

      + {{RTCSignalingState/"stable"}}, {{RTCSignalingState/"have-local-offer"}}, + or {{RTCSignalingState/"have-remote-pranswer"}}; otherwise + {{RTCSdpType/"answer"}}.

    7. -

      If type is "offer", and +

      If type is {{RTCSdpType/"offer"}}, and sdp is not the empty string and not equal to connection.[[\LastCreatedOffer]], then return a promise [= rejected =] with a newly @@ -2808,8 +2808,8 @@

      Methods

      steps.

    8. -

      If type is "answer" or - "pranswer", and sdp is not the +

      If type is {{RTCSdpType/"answer"}} or + {{RTCSdpType/"pranswer"}}, and sdp is not the empty string and not equal to connection.[[\LastCreatedAnswer]], then return a promise [= rejected =] with a newly [= exception/create | created =] @@ -2818,7 +2818,7 @@

      Methods

    9. If sdp is the empty string, and - type is "offer", then run the + type is {{RTCSdpType/"offer"}}, then run the following sub steps:

      1. @@ -2841,8 +2841,8 @@

        Methods

      2. If sdp is the empty string, and - type is "answer" or - "pranswer", then run the following sub + type is {{RTCSdpType/"answer"}} or + {{RTCSdpType/"pranswer"}}, then run the following sub steps:

        1. @@ -2916,7 +2916,7 @@

          Methods

          1. If the description's {{RTCSessionDescriptionInit/type}} is - "offer" and is invalid for the + {{RTCSdpType/"offer"}} and is invalid for the current [= signaling state =] of connection as described in [[!JSEP]], @@ -3194,7 +3194,7 @@

            Methods

          2. Set connection's [= signaling state =] to - "closed".

            + {{RTCSignalingState/"closed"}}.

          3. Let transceivers be the result of executing the @@ -3215,7 +3215,7 @@

            Methods

          4. Set the [[\ReadyState]] slot of each of connection's {{RTCDataChannel}}s - to "{{RTCDataChannelState/closed}}"

            + to {{RTCDataChannelState/"closed"}}

            The {{RTCDataChannel}}s will be closed abruptly and the closing procedure will not be invoked.
            @@ -3224,12 +3224,12 @@

            Methods

            If the connection.[[\SctpTransport]] is not null, tear down the underlying SCTP association by sending an SCTP ABORT chunk and set the - [[\SctpTransportState]] to "{{RTCSctpTransportState/closed}}".

            + [[\SctpTransportState]] to {{RTCSctpTransportState/"closed"}}.

          5. Set the [[\DtlsTransportState]] slot of each of connection's {{RTCDtlsTransport}}s - to "{{RTCDtlsTransportState/closed}}".

            + to {{RTCDtlsTransportState/"closed"}}.

          6. Destroy connection's [= ICE Agent =], @@ -3240,16 +3240,16 @@

            Methods

          7. Set the [[\IceTransportState]] slot of each of connection's {{RTCIceTransport}}s - to "{{RTCIceTransportState/closed}}".

            + to {{RTCIceTransportState/"closed"}}.

          8. Set connection's [= ICE connection state =] to - "closed". This does not fire any event. + {{RTCIceConnectionState/"closed"}}. This does not fire any event.

          9. Set connection's [= connection state =] to - "closed".

            + {{RTCPeerConnectionState/"closed"}}.

          @@ -3690,7 +3690,7 @@

          RTCSdpType

          rollback -

          An RTCSdpType of rollback +

          An RTCSdpType of {{RTCSdpType/"rollback"}} indicates that a description MUST be treated as canceling the current SDP negotiation and moving the SDP [[!SDP]] offer back to what it was in the previous stable state. Note @@ -3784,7 +3784,7 @@

          Dictionary RTCSessionDescriptionInit
          sdp of type DOMString
          The string representation of the SDP [[!SDP]]; if - type is "rollback", this member is unused. + type is {{RTCSdpType/"rollback"}}, this member is unused.
          @@ -3846,7 +3846,7 @@

          Updating the Negotiation-Needed flag

        2. If connection's [= signaling state =] is not - "stable", abort these steps.

          + {{RTCSignalingState/"stable"}}, abort these steps.

          The negotiation-needed flag will be updated once the state transitions to "stable", as part of the steps @@ -3934,7 +3934,7 @@

          Updating the Negotiation-Needed flag

          1. If transceiver.[[\Direction]] is - "sendrecv" or "sendonly", + {{RTCRtpTransceiverDirection/"sendrecv"}} or {{RTCRtpTransceiverDirection/"sendonly"}}, and the [= associated =] m= section in description either doesn't contain a single "a=msid" line, or the number of MSIDs from the "a=msid" lines in this m= section, @@ -3944,7 +3944,7 @@

            Updating the Negotiation-Needed flag

          2. -

            If description is of type "offer", +

            If description is of type {{RTCSdpType/"offer"}}, and the direction of the [= associated =] m= section in neither connection.[[\CurrentLocalDescription]] nor @@ -3957,7 +3957,7 @@

            Updating the Negotiation-Needed flag

            view.

          3. -

            If description is of type "answer", +

            If description is of type {{RTCSdpType/"answer"}}, and the direction of the [= associated =] m= section in the description does not match transceiver.[[\Direction]] @@ -4435,14 +4435,14 @@

            RTCPeerConnectionIceEvent

            All {{RTCIceTransport}}s have finished gathering candidates, and the {{RTCPeerConnection}}'s {{RTCIceGatheringState}} has transitioned to - "{{RTCIceGatheringState/complete}}". + {{RTCIceGatheringState/"complete"}}. This is indicated by the {{RTCPeerConnectionIceEvent/candidate}} member of the event being set to null. This only exists for backwards compatibility, and this event does not need to be signaled to the remote peer. It's equivalent to an "{{icegatheringstatechange}}" event with the - "{{RTCIceGatheringState/complete}}" + {{RTCIceGatheringState/"complete"}} state.

          4. @@ -5534,7 +5534,7 @@

            Dictionary RTCRtpTransceiverInit "RTCRtpTransceiverInit" class="dictionary-members">
            direction of type {{RTCRtpTransceiverDirection}}, - defaulting to "sendrecv"
            + defaulting to {{RTCRtpTransceiverDirection/"sendrecv"}}
            The direction of the {{RTCRtpTransceiver}}.
            streams of type sequence<{{MediaStream}}>
            @@ -5619,8 +5619,8 @@

            Dictionary RTCRtpTransceiverInit

            Processing Remote MediaStreamTracks

            An application can reject incoming media descriptions by setting - the transceiver's direction to either "inactive" to turn - off both directions temporarily, or to "sendonly" to reject + the transceiver's direction to either {{RTCRtpTransceiverDirection/"inactive"}} to turn + off both directions temporarily, or to {{RTCRtpTransceiverDirection/"sendonly"}} to reject only the incoming side. To permanently reject an m-line in a manner that makes it available for reuse, the application would need to call RTCRtpTransceiver.{{RTCRtpTransceiver/stop}}() @@ -5637,23 +5637,23 @@

            Processing Remote MediaStreamTracks

            addList, and removeList.

          5. -

            If direction is "sendrecv" or - "recvonly" and transceiver.[[\FiredDirection]] - is neither "sendrecv" nor "recvonly", +

            If direction is {{RTCRtpTransceiverDirection/"sendrecv"}} or + {{RTCRtpTransceiverDirection/"recvonly"}} and transceiver.[[\FiredDirection]] + is neither {{RTCRtpTransceiverDirection/"sendrecv"}} nor {{RTCRtpTransceiverDirection/"recvonly"}}, or the previous step increased the length of addList, process the addition of a remote track with transceiver and trackEventInits.

          6. -

            If direction is "sendonly" or - "inactive", set transceiver.[[\Receptive]] +

            If direction is {{RTCRtpTransceiverDirection/"sendonly"}} or + {{RTCRtpTransceiverDirection/"inactive"}}, set transceiver.[[\Receptive]] to false.

          7. -

            If direction is "sendonly" or - "inactive", and +

            If direction is {{RTCRtpTransceiverDirection/"sendonly"}} or + {{RTCRtpTransceiverDirection/"inactive"}}, and transceiver.[[\FiredDirection]] - is either "sendrecv" or "recvonly", + is either {{RTCRtpTransceiverDirection/"sendrecv"}} or {{RTCRtpTransceiverDirection/"recvonly"}}, process the removal of a remote track for the media description, with transceiver and muteTracks.

            @@ -6168,7 +6168,7 @@

            Methods

          8. Let sending be true if the transceiver.[[\CurrentDirection]] - is "sendrecv" or "sendonly", + is {{RTCRtpTransceiverDirection/"sendrecv"}} or {{RTCRtpTransceiverDirection/"sendonly"}}, and false otherwise.

          9. @@ -7227,7 +7227,7 @@

            Attributes

          10. If transceiver.[[\Stopping]] is - true, return "stopped".

            + true, return {{RTCRtpTransceiverDirection/"stopped"}}.

          11. Otherwise, return the value of the [[\Direction]] @@ -7263,7 +7263,7 @@

            Attributes

          12. If newDirection is equal to - "stopped", [= exception/throw =] a {{TypeError}}. + {{RTCRtpTransceiverDirection/"stopped"}}, [= exception/throw =] a {{TypeError}}.

          13. @@ -7289,7 +7289,7 @@

            Attributes

            deduced from the other. If this transceiver has never been represented in an offer/answer exchange, the value is null. If the transceiver is - {{stopped}}, the value is "stopped". + {{stopped}}, the value is {{RTCRtpTransceiverDirection/"stopped"}}.

            On getting, the user agent MUST run the following steps:

              @@ -7300,7 +7300,7 @@

              Attributes

            1. If transceiver.[[\Stopped]] is - true, return "stopped".

              + true, return {{RTCRtpTransceiverDirection/"stopped"}}.

            2. Otherwise, return the value of the @@ -8306,8 +8306,8 @@

              Methods

              Returns the selected candidate pair on which packets are sent. This method MUST return the value of the [[\SelectedCandidatePair]] - slot. When {{RTCIceTransport}}.state is "new" or - "closed" getSelectedCandidatePair returns + slot. When {{RTCIceTransport}}.state is {{RTCIceTransportState/"new"}} or + {{RTCIceTransportState/"closed"}} getSelectedCandidatePair returns null.

              getLocalParameters
              @@ -8518,18 +8518,18 @@

              RTCIceTransportState Enum

              checking -> connected -> completed, but under specific circumstances (only the last checked candidate succeeds, and gathering and the no-more candidates indication both occur prior to success), the - state can transition directly from "checking" to "completed". + state can transition directly from {{RTCIceTransportState/"checking"}} to {{RTCIceTransportState/"completed"}}.

              An ICE restart causes candidate gathering and connectity checks to - begin anew, causing a transition to connected if begun in the - completed state. If begun in the transient - disconnected state, it causes a transition to - checking, effectively forgetting that connectivity was + begin anew, causing a transition to {{RTCIceTransportState/"connected"}} if begun in the + {{RTCIceTransportState/"completed"}} state. If begun in the transient + {{RTCIceTransportState/"disconnected"}} state, it causes a transition to + {{RTCIceTransportState/"checking"}}, effectively forgetting that connectivity was previously lost.

              -

              The failed and completed states require an +

              The {{RTCIceTransportState/"failed"}} and {{RTCIceTransportState/"completed"}} states require an indication that there are no additional remote candidates. This can be indicated by calling {{RTCPeerConnection/addIceCandidate}} with - a candidate value whose candidate property is set + a candidate value whose {{RTCIceCandidate/candidate}} property is set to an empty string or by {{RTCPeerConnection/canTrickleIceCandidates}} being set to false.

              Some example state transitions are:

              @@ -9150,7 +9150,7 @@

              RTCSctpTransportState Enum

              When the negotiation of an association is completed, a task is queued to update the [[\SctpTransportState]] slot to - "connected".

              + {{RTCSctpTransportState/"connected"}}.

              @@ -9158,7 +9158,7 @@

              RTCSctpTransportState Enum

              "idl-def-RTCSctpTransportState.closed">closed

              A task is queued to update the [[\SctpTransportState]] - slot to "closed" when: + slot to {{RTCSctpTransportState/"closed"}} when:

              • a SHUTDOWN or ABORT chunk @@ -9252,7 +9252,7 @@

                Creating a data channel

              • Let channel have a [[\ReadyState]] internal - slot initialized to "connecting".

                + slot initialized to {{RTCDataChannelState/"connecting"}}.

              • Let channel have a [[\BufferedAmount]] @@ -9288,12 +9288,12 @@

                Announcing a data channel as open

                object to be announced.

              • -

                If channel.[[\ReadyState]] is "closing" or - "closed", abort these steps.

                +

                If channel.[[\ReadyState]] is {{RTCDataChannelState/"closing"}} or + {{RTCDataChannelState/"closed"}}, abort these steps.

              • Set channel.[[\ReadyState]] to - "open".

                + {{RTCDataChannelState/"open"}}.

              • [= Fire an event =] named {{open}} at @@ -9339,7 +9339,7 @@

                Announcing a data channel instance

              • Set channel.[[\ReadyState]] to - "open" (but do not fire the {{open}} + {{RTCDataChannelState/"open"}} (but do not fire the {{open}} event, yet).

                This allows to start sending messages inside of the {{datachannel}} event handler prior to the @@ -9375,7 +9375,7 @@

                Closing procedure

                Unless the procedure was initiated by the channel's {{RTCDataChannel/close}} method, set channel.[[\ReadyState]] to - "closing".

                + {{RTCDataChannelState/"closing"}}.

              • Run the following steps in parallel:

                @@ -9414,7 +9414,7 @@

                Announcing a data channel as closed

              • Set channel.[[\ReadyState]] to - "closed".

                + {{RTCDataChannelState/"closed"}}.

              • If the [= underlying data transport | transport =] was closed @@ -9449,7 +9449,7 @@

                Error on creating data channels

              • Set channel.[[\ReadyState]] to - "closed".

                + {{RTCDataChannelState/"closed"}}.

              • [= Fire an event =] named {{RTCDataChannel/error}} using the @@ -9483,7 +9483,7 @@

                Receiving messages on a data channel

              • If channel.[[\ReadyState]] is not - "open", abort these steps and discard rawData. + {{RTCDataChannelState/"open"}}, abort these steps and discard rawData.

              • @@ -9654,7 +9654,7 @@

                Attributes

                protocol, or buffering done by the operating system or network hardware. The value of the [[\BufferedAmount]] slot will only increase with each call to the {{RTCDataChannel/send()}} method as long as the - [[\ReadyState]] slot is "open"; however, the + [[\ReadyState]] slot is {{RTCDataChannelState/"open"}}; however, the slot does not reset to zero once the channel closes. When the [= underlying data transport =] sends data from its queue, the user agent MUST queue a task that reduces @@ -9740,12 +9740,12 @@

                Methods

              • If channel.[[\ReadyState]] is - "closing" or "closed", then abort these + {{RTCDataChannelState/"closing"}} or {{RTCDataChannelState/"closed"}}, then abort these steps.

              • Set channel.[[\ReadyState]] to - "closing".

                + {{RTCDataChannelState/"closing"}}.

              • If the [= closing procedure =] has not @@ -9791,7 +9791,7 @@

                Methods

              • If channel.[[\ReadyState]] is not - "open", [= exception/throw =] an + {{RTCDataChannelState/"open"}}, [= exception/throw =] an {{InvalidStateError}}.

              • @@ -10036,19 +10036,19 @@

                Garbage Collection

                • [[\ReadyState]] slot is - "connecting" and at least one event listener is registered + {{RTCDataChannelState/"connecting"}} and at least one event listener is registered for open events, message events, error events, or close events.

                • [[\ReadyState]] slot is - "open" and at least one event listener is registered for + {{RTCDataChannelState/"open"}} and at least one event listener is registered for message events, error events, or close events.

                • [[\ReadyState]] slot is - "closing" and at least one event listener is registered + {{RTCDataChannelState/"closing"}} and at least one event listener is registered for error events, or close events.

                • @@ -10272,12 +10272,12 @@

                  canInsertDTMF algorithm

                  associated with sender.
                • Let connection be the {{RTCPeerConnection}} associated with transceiver.
                • -
                • If connection's {{RTCPeerConnectionState}} is not "connected" +
                • If connection's {{RTCPeerConnectionState}} is not {{RTCPeerConnectionState/"connected"}} return false.
                • If sender.[[\SenderTrack]] is null return false.
                • -
                • If transceiver.[[\CurrentDirection]] is neither "sendrecv" - nor "sendonly" return false.
                • +
                • If transceiver.[[\CurrentDirection]] is neither {{RTCRtpTransceiverDirection/"sendrecv"}} + nor {{RTCRtpTransceiverDirection/"sendonly"}} return false.
                • If sender.[[\SendEncodings]][0].active is false return false.
                • If no codec with mimetype "audio/telephone-event" has been @@ -11336,7 +11336,7 @@

                  Perfect Negotiation Example

                  application. This pattern has advantages over other patterns, like one side always being the offerer, as it lets applications operate on both peer connection objects simultaneously without risk of glare (an offer - coming in outside of "stable" state). The rest of the + coming in outside of {{RTCSignalingState/"stable"}} state). The rest of the application may use any and all modification methods and attributes, without worrying about signaling state races.

                  @@ -11493,21 +11493,21 @@

                  Attributes

                  sdpLineNumber of type long, readonly, nullable
                  -

                  If errorDetail is "sdp-syntax-error" +

                  If errorDetail is {{RTCErrorDetailType/"sdp-syntax-error"}} this is the line number where the error was detected (the first line has line number 1).

                  sctpCauseCode of type long, readonly, nullable
                  -

                  If errorDetail is "sctp-failure" this +

                  If errorDetail is {{RTCErrorDetailType/"sctp-failure"}} this is the SCTP cause code of the failed SCTP negotiation.

                  receivedAlert of type unsigned long, readonly, nullable
                  -

                  If errorDetail is "dtls-failure" and +

                  If errorDetail is {{RTCErrorDetailType/"dtls-failure"}} and a fatal DTLS alert was received, this is the value of the DTLS alert received.

                  @@ -11515,7 +11515,7 @@

                  Attributes

                  class="idlAttrType">unsigned long, readonly, nullable
                  -

                  If errorDetail is "dtls-failure" and +

                  If errorDetail is {{RTCErrorDetailType/"dtls-failure"}} and a fatal DTLS alert was sent, this is the value of the DTLS alert sent.