diff --git a/index.html b/index.html index ee9db06..e58a9b9 100644 --- a/index.html +++ b/index.html @@ -457,7 +457,6 @@

Dictionary {{RTCResolutionRestriction}} Members

restrictions are orientation agnostic, see note below. When scaling is applied, both dimensions of the frame MUST be downscaled using the same factor.

-

The restrictions being orientation agnostic means that they will automatically be adjusted to the orientation of the frame being @@ -466,6 +465,7 @@

Dictionary {{RTCResolutionRestriction}} Members

720x1280 is specified, both always result in the exact same scaling factor regardless of the orientation of the frame.

+ @@ -1292,8 +1292,7 @@

Transferable Data Channels

-

This section extends {{RTCDataChannel}} by making it transferable.

-

This allows sending and receiving messages outside the context the connection was created, for instance in workers or third-party iframes.

+

This section extends {{RTCDataChannel}} by exposing it to any type of {{Worker}} (not just DedicatedWorker).

The WebIDL changes are the following: 

@@ -1301,58 +1300,6 @@ 

   partial interface RTCDataChannel {
 };
-
-

The create an RTCDataChannel algorithm is updated by adding the following steps after step 4 of the original algorithm:

-
    -

  1. Initialize channel.`[[IsTransferable]]` to true.

    2. -

  2. Queue a task to run the following step:

    -
      -

    1. Set channel.`[[IsTransferable]]` to false.

      2. -
    -
    3. -
-

This task needs to run before any task enqueued by the receiving messages on a data channel algorithm for channel. - This ensures that no message is lost during the transfer of a {{RTCDataChannel}}.

-
-
The send() algorithm is modified by adding the following step after step 1 of the original algorithm: -
    -

  1. Set channel.`[[IsTransferable]]` to false.

    2. -
-
-
-

The {{RTCDataChannel}} transfer steps, given value and dataHolder, are:

-
    -

  1. If value.`[[IsTransferable]]` is false, throw a "DataCloneError" DOMException.

    2. -

  2. Set dataHolder.`[[ReadyState]]` to value.`[[ReadyState]]`.

    3. -

  3. Set dataHolder.`[[DataChannelLabel]]` to value.`[[DataChannelLabel]]`.

    4. -

  4. Set dataHolder.`[[Ordered]]` to value.`[[Ordered]]`.

    5. -

  5. Set dataHolder.`[[MaxPacketLifeTime]]` to value..`[[MaxPacketLifeTime]]`

    6. -

  6. Set dataHolder.`[[MaxRetransmits]]` to value.`[[MaxRetransmits]]`.

    7. -

  7. Set dataHolder.`[[DataChannelProtocol]]` to value.`[[DataChannelProtocol]]`.

    8. -

  8. Set dataHolder.`[[Negotiated]]` to value.`[[Negotiated]]`.

    9. -

  9. Set dataHolder.`[[DataChannelId]]` to value.`[[DataChannelId]]`.

    10. -

  10. Set dataHolder.`[[underlyingDataTransport]]` to value underlying data transport.

    11. -

  11. Set value.`[[IsTransferable]]` to false.

    12. -

  12. Set value.`[[ReadyState]]` to "closed".

    13. -
-
-

The {{RTCDataChannel}} [=transfer-receiving steps=], given dataHolder and channel, are:

-
    -

  1. Initialize channel.`[[ReadyState]]` to dataHolder.`[[ReadyState]]`.

    2. -

  2. Initialize channel.`[[DataChannelLabel]]` to dataHolder.`[[\DataChannelLabel]]`.

    3. -

  3. Initialize channel.`[[Ordered]]` to dataHolder.`[[Ordered]]`.

    4. -

  4. Initialize channel.`[[MaxPacketLifeTime]]` to dataHolder.`[[MaxPacketLifeTime]]`.

    5. -

  5. Initialize channel.`[[MaxRetransmits]]` to dataHolder.`[[MaxRetransmits]]`.

    6. -

  6. Initialize channel.`[[DataChannelProtocol]]` to dataHolder.`[[DataChannelProtocol]]`.

    7. -

  7. Initialize channel.`[[Negotiated]]` to dataHolder.`[[Negotiated]]`.

    8. -

  8. Initialize channel.`[[DataChannelId]]` to dataHolder.`[[DataChannelId]]`.

    9. -

  9. Initialize channel underlying data transport to dataHolder.`[[underlyingDataTransport]]`.

    10. -
-

The above steps do not need to transfer `[[BufferedAmount]]` as its value will always be equal to 0. - The reason is an {{RTCDataChannel}} can be transferred only if its send() algorithm was not called prior the transfer.

-

If the underlying data transport is closed at the time of the [=transfer-receiving steps=], - the {{RTCDataChannel}} object will be closed by running the announcing a data channel as closed algorithm immediately after the [=transfer-receiving steps=].

-