From 35f4aa990713d3a3441714ce8bf9c3bc58463094 Mon Sep 17 00:00:00 2001 From: Anssi Kostiainen Date: Tue, 10 Oct 2017 10:56:53 +0300 Subject: [PATCH] Fix ReSpec warnings Specific changes: Global -> Global -> Add presentation displays Add
    Add
      Add
      presentation -> presentation instance of the Presentation -> instance of the Presentation --- index.html | 198 ++++++++++++++++++++++++++--------------------------- 1 file changed, 99 insertions(+), 99 deletions(-) diff --git a/index.html b/index.html index fb223ec..328e906 100644 --- a/index.html +++ b/index.html @@ -892,18 +892,18 @@

      Common idioms

      - A presentation + A presentation display refers to a graphical and/or audio output device available to the user agent via an implementation specific connection technology.

      - A presentation connection is an object relating a controlling browsing context to its receiving browsing context and enables two-way-messaging between them. Each presentation connection - has a presentation connection state, a unique presentation connection state, a unique presentation identifier to distinguish it from other presentations, and a presentation URL that is a URL used to create @@ -917,21 +917,21 @@

      subset of Web content because of functional, security or hardware limitations. Examples are set-top boxes, smart TVs, or networked speakers capable of rendering only audio. We say that such a display - is an available presentation display for a presentation URL if the controlling user agent can reasonably guarantee that presentation of the URL on that display will succeed.

      - A controlling browsing context (or controller for short) is a browsing context that has connected to a presentation by calling - start or start or reconnect, or received a presentation - connection via a via a connectionavailable event. In algorithms for PresentationRequest, the controlling browsing context is the responsible browsing context whose @@ -1011,7 +1011,7 @@

      objects constructed by algorithm steps is the current realm.

      -
      +

      Interface Presentation

      @@ -1026,8 +1026,8 @@

      - The presentation attribute is - used to retrieve an instance of the Presentation + The presentation attribute is + used to retrieve an instance of the Presentation interface. It MUST return the Presentation instance.

      @@ -1070,7 +1070,7 @@

      If a controlling user agent does not support starting a presentation from a default presentation request, that user - agent should ignore any value set for defaultRequest.

      @@ -1212,7 +1212,7 @@

      presentationRequest, the PresentationRequest - object that received the call to start
      @@ -1231,7 +1231,7 @@

      context of the controlling browsing context.
    1. If there is already an unsettled Promise from a previous - call to start in + call to start in topContext or any browsing context in the list of descendant browsing contexts of topContext, return a new Promise rejected with an OperationError @@ -1406,7 +1406,7 @@

      list of available presentation displays.

    2. Set the presentation connection state of S to - connecting. + connecting.
    3. Add S to the set of controlled presentations.
      4. @@ -1415,9 +1415,9 @@

    4. Queue a task to fire a trusted event with - the name connectionavailable, + the name connectionavailable, that uses the PresentationConnectionAvailableEvent - interface, with the connection attribute initialized to S, at presentationRequest. The event must not bubble, must not be cancelable, and has no @@ -1426,7 +1426,7 @@

    5. Let U be the user agent connected to D.
    6. If the next step fails, abort all remaining steps and close - the presentation connection S with S with error as closeReason, and a human readable message describing the failure as closeMessage. @@ -1462,7 +1462,7 @@

      7. presentationRequest, the PresentationRequest - object that reconnect was called + object that reconnect was called on
      @@ -1487,7 +1487,7 @@

    7. Its controlling browsing context is the current browsing context
      8. -
    8. Its presentation connection state is not Its presentation connection state is not terminated
    9. Its presentation URL is equal to one of the @@ -1510,13 +1510,13 @@

      existingConnection.

    10. If the presentation connection state of - existingConnection is connecting or existingConnection is connecting or connected, then abort all remaining steps.
    11. Set the presentation connection state of - existingConnection to existingConnection to connecting.
    12. @@ -1533,7 +1533,7 @@

    13. Its controlling browsing context is not the current browsing context
      14. -
    14. Its presentation connection state is not Its presentation connection state is not terminated
    15. Its presentation URL is equal to one of the @@ -1562,7 +1562,7 @@

      existingConnection.

    16. Set the presentation connection state of - newConnection to newConnection to connecting.
    17. Add newConnection to the set of controlled @@ -1573,10 +1573,10 @@

    18. Queue a task to fire a trusted event - with the name connectionavailable, that uses the PresentationConnectionAvailableEvent interface, with - the connection attribute initialized to newConnection, at presentationRequest. The event must not bubble, @@ -1658,7 +1658,7 @@

      If the controlling user agent can monitor the list of available presentation displays in the background (without a - pending request to start), the + pending request to start), the PresentationAvailability object MUST be implemented in a controlling browsing context.

      @@ -1679,7 +1679,7 @@

      The user agent MUST keep track of the set of - presentation availability objects created by the created by the getAvailability method. The set of presentation availability objects is represented as a set of tuples (A, availabilityUrls), @@ -1691,7 +1691,7 @@

    19. availabilityUrls is the list of presentation - request URLs for the PresentationRequest when for the PresentationRequest when getAvailability was called on it to create A.
      20. @@ -1718,12 +1718,12 @@

      While the set of presentation availability objects is not empty, the user agent MAY monitor the list of available presentation displays continuously, so that pages can use the - value property of a + value property of a PresentationAvailability object to offer presentation only when there are available displays. However, the user agent may not support continuous availability monitoring in the background; for example, because of platform or power consumption - restrictions. In this case the Promise returned by Promise returned by getAvailability is rejected, and the algorithm to monitor the list of available presentation displays will only run as part of the @@ -1756,7 +1756,7 @@

      presentationRequest, the PresentationRequest - object that received the call to getAvailability
      @@ -1768,7 +1768,7 @@

      1. If there is an unsettled Promise from a previous call to - getAvailability on + getAvailability on presentationRequest, return that Promise and abort these steps.
        2. @@ -1831,7 +1831,7 @@

        If the set of presentation availability objects is - non-empty, or there is a pending request to select a presentation display, the user agent MUST monitor the list of available presentation displays by running the following @@ -1841,7 +1841,7 @@

      2. Let availabilitySet be a shallow copy of the set of presentation availability objects.
        3. -
      3. If there is a pending request to If there is a pending request to select a presentation display for a PresentationRequest and if the PresentationRequest's presentation display availability is null, then @@ -1873,7 +1873,7 @@

      4. For each member (A, availabilityUrls) of availabilitySet, run the following steps: -
          +
          1. Set previousAvailability to the value of A's value property.
            2. @@ -1922,8 +1922,8 @@

            The controlling user agent may choose how often to monitor the list of available presentation displays, - including grouping requests from start and start and getAvailability, and aggregating them across browsing contexts.
            @@ -1941,7 +1941,7 @@

            availability objects.
          2. If the set of presentation availability objects is now - empty and there is no pending request to select a presentation display, cancel any pending task to monitor the list of available presentation displays for power saving purposes, and @@ -1974,27 +1974,27 @@

            A controlling user agent fires a trusted event - named connectionavailable on a + named connectionavailable on a PresentationRequest when a connection associated with the object is created. It is fired at the PresentationRequest instance, using the PresentationConnectionAvailableEvent - interface, with the connection attribute set to the PresentationConnection object that was created. The event is fired for each connection that is created for the controller, either by the controller calling - start or start or reconnect, or by the controlling user agent creating a connection on the controller's behalf via - defaultRequest. + defaultRequest.

            A receiving user agent fires a trusted event - named connectionavailable + named connectionavailable on a PresentationReceiver when an incoming connection is created. It is fired at the presentation controllers monitor, using the PresentationConnectionAvailableEvent - interface, with the connection attribute set to the PresentationConnection object that was created. The event is fired for all connections that are created @@ -2009,7 +2009,7 @@

            When the PresentationConnectionAvailableEvent constructor is called, the user agent MUST construct a new - PresentationConnectionAvailableEvent object with its PresentationConnectionAvailableEvent object with its connection attribute set to the connection member @@ -2083,7 +2083,7 @@

          3. closed means that the presentation connection has been closed, or could not be opened. It may be re-opened - through a call to reconnect. No + through a call to reconnect. No communication is possible.
          4. @@ -2098,7 +2098,7 @@

            When the close method is called on a PresentationConnection S, the user agent MUST start closing the presentation connection S - with closed as + with closed as closeReason and an empty message as closeMessage.

            @@ -2145,10 +2145,10 @@

            When a PresentationConnection object S is discarded (because the document owning it is navigating or is closed) while the presentation connection state of - S is connecting - or connected, the user + S is connecting + or connected, the user agent MUST start closing the presentation connection - S with S with wentaway as closeReason and an empty closeMessage.

            @@ -2156,8 +2156,8 @@

            If the user agent receives a signal from the destination browsing context that a PresentationConnection S is to be closed, it MUST close the presentation - connection S with closed or S with closed or wentaway as closeReason and an empty closeMessage.

            @@ -2182,7 +2182,7 @@

            1. If the presentation connection state of - presentationConnection is not presentationConnection is not connecting, then abort all remaining steps.
              2. @@ -2195,7 +2195,7 @@

              run the following steps:
              1. Set the presentation connection state of - presentationConnection to presentationConnection to connected.
              2. @@ -2206,7 +2206,7 @@

            2. If the connection cannot be completed, close the - presentation connection S with S with error as closeReason, and a human readable message describing the failure as closeMessage. @@ -2229,7 +2229,7 @@

              No specific transport for the connection between the controlling browsing context and the receiving browsing context is - mandated, except that for multiple calls to send it has to be ensured that messages are delivered to the other end reliably and in sequence. The transport should function equivalently to an @@ -2259,9 +2259,9 @@

              send to the other browsing context

      20. -
        +
        1. If the state property of - presentationConnection is not presentationConnection is not connected, throw an InvalidStateError exception.
          2. @@ -2282,7 +2282,7 @@

        2. If the previous step encounters an unrecoverable error, then abruptly close the presentation connection - presentationConnection with presentationConnection with error as closeReason, and a closeMessage describing the error encountered. @@ -2348,9 +2348,9 @@

          the message -
            +
            1. If the state property of - presentationConnection is not presentationConnection is not connected, abort these steps.
            2. Let event be a newly created trusted event @@ -2389,7 +2389,7 @@

              receiving a message through presentationConnection, it MUST abruptly close the presentation connection presentationConnection with - error as + error as closeReason. It SHOULD use a human readable description of the error encountered as closeMessage.

              @@ -2417,7 +2417,7 @@

              A PresentationConnectionCloseEvent is fired when a - presentation connection enters a presentation connection enters a closed state. The reason attribute provides the reason why the connection was closed. It can take one of the @@ -2431,7 +2431,7 @@

            3. closed means that either the controlling browsing context or the receiving browsing context that were - connected by the PresentationConnection called PresentationConnection called close.
            4. @@ -2441,8 +2441,8 @@

              5. - When the reason - attribute is error, + When the reason + attribute is error, the user agent SHOULD set the message attribute to a human readable description of how the communication channel @@ -2451,11 +2451,11 @@

              When the PresentationConnectionCloseEvent constructor is called, the user agent MUST construct a new - PresentationConnectionCloseEvent object, with its PresentationConnectionCloseEvent object, with its reason attribute set to the reason member of the PresentationConnectionCloseEventInit object - passed to the constructor, and its message attribute set to the message member of this PresentationConnectionCloseEventInit object @@ -2491,13 +2491,13 @@

              1. If the presentation connection state of - presentationConnection is not connecting or presentationConnection is not connecting or connected then abort the remaining steps.
              2. Set the presentation connection state of - presentationConnection to presentationConnection to closed.
              3. Start to signal to the destination browsing context the @@ -2507,7 +2507,7 @@

                PresentationConnection was actually closed before proceeding to the next step.

                4. -
              4. If closeReason is not If closeReason is not wentaway, then locally run the steps to close the presentation connection with presentationConnection, closeReason, and @@ -2547,15 +2547,15 @@

                Queue a task to run the following steps:
                1. If the presentation connection state of - presentationConnection is not connecting, connected, or presentationConnection is not connecting, connected, or closed, then abort the remaining steps.
                2. If the presentation connection state of - presentationConnection is not closed, set it to presentationConnection is not closed, set it to closed.
                3. If the presentationConnection was created as a @@ -2572,12 +2572,12 @@

              5. - Fire a trusted event with the name Fire a trusted event with the name close, that uses the PresentationConnectionCloseEvent interface, with the - reason + reason attribute initialized to closeReason and the - message + message attribute initialized to closeMessage, at presentationConnection. The event must not bubble, must not be cancelable, and has no default action. @@ -2598,8 +2598,8 @@

                1. If the presentation connection state of - connection is not - connected or connection is not + connected or connecting, then abort these steps.
                  2. @@ -2610,17 +2610,17 @@

                2. If the presentation identifier of known connection and connection are equal, and the presentation connection state of known - connection is connected or is connected or connecting, then queue a task to run the following steps:
                  1. Set the presentation connection state of - known connection to known connection to terminated.
                  2. - Fire a simple event named Fire a simple event named terminate at known connection.
                    3. @@ -2680,12 +2680,12 @@

                    run the following steps:
                    1. If the presentation connection state of - connection is + connection is connected, then add connection to connectedControllers.
                    2. Set the presentation connection state of - connection to + connection to terminated.
                    @@ -2724,17 +2724,17 @@

                    task to run the following steps:
                    1. If the presentation connection state of - connection is not connected or connection is not connected or connecting, then abort the following steps.
                    2. Set the presentation connection state of - connection to + connection to terminated.
                    3. - Fire a simple event named Fire a simple event named terminate at connection.
                      4. @@ -3046,9 +3046,9 @@

                      mechanism.
                    4. If connection establishment completes successfully, set the - presentation connection state of S to of S to connected. Otherwise, set the - presentation connection state of S to presentation connection state of S to closed and abort all remaining steps.
                      5. @@ -3081,10 +3081,10 @@

                    5. Queue a task to fire a trusted event - with the name connectionavailable, that uses the PresentationConnectionAvailableEvent - interface, with the connection attribute initialized to S, at the presentation controllers monitor. The event must not bubble, must not @@ -3185,14 +3185,14 @@

                      browsing context obtains the presentation URL and presentation identifier of a running presentation from the user, local storage, or a server, and then connects to the - presentation via reconnect. + presentation via reconnect.

                      This specification makes no guarantee as to the identity of any party connecting to a presentation. Once connected, the presentation may wish to further verify the identity of the connecting party through application-specific means. For example, the presentation could - challenge the controller to provide a token via send that the presentation uses to verify identity and authorization.