From b24d28c782e56af5674f0b14fca59453b3521fa5 Mon Sep 17 00:00:00 2001 From: Daniel Davis Date: Wed, 2 Jul 2014 16:59:27 +0900 Subject: [PATCH 1/2] Fixed a few typos --- index.html | 24 ++++++++++++------------ 1 file changed, 12 insertions(+), 12 deletions(-) diff --git a/index.html b/index.html index 9363fe2..7e08969 100644 --- a/index.html +++ b/index.html @@ -195,11 +195,11 @@

1 Introduction

It is the intention of this specification that the user agent prepares a rendering for the secondary display in a way that is adapted to the secondary display's capabilities. The DOM state and the rendering shown on the primary and - secondary display are maintained and perfomend by the same user agent. There is no secondary user agent involved + secondary display are maintained and performed by the same user agent. There is no secondary user agent involved that would run remotely on the secondary display.

The user agent creates two browsing contexts, one on the primary display, one on the selected presentation - display. It is responsible for sending the rendered output to the secondary display. For wirelessly connected + display. It is responsible for sending the rendered output to the secondary display. For wirelessly-connected displays this may mean that the user agent prepares a video stream from the rendering output that is sent over the network to the wireless display.

@@ -314,7 +314,7 @@

2 Conformance

Requirements phrased in the imperative as part of algorithms (such as "strip any leading space characters" or "return false and terminate these steps") are to be interpreted with the meaning of the -key word ("must", "should", "may", etc) used in introducing the +key word ("must", "should", "may", etc.) used in introducing the algorithm.

Conformance requirements phrased as algorithms or specific steps @@ -398,13 +398,13 @@

6 Display system via wired connections (e.g. HDMI, DVI etc.) as well as via wireless technologies (e.g. MiraCast, DLNA or similar) that use a local or personal area network as a transport mechanism. The - discovery can be performend by using operating system APIs that - notifiy the user agent about display configuration changes or by + discovery can be performed by using operating system APIs that + notify the user agent about display configuration changes or by means of network discovery for remote display technologies that are not handled by the operating system. In the latter case, the user agent or the operating system that the user agent runs on may prepare a video stream suitable for being decoded and displayed by - the wirelessly connected display.

+ the wirelessly-connected display.

6.1 Monitoring for Availability Changes

@@ -467,10 +467,10 @@

7 Requesti created auxiliary browsing context is called presentation browsing context.
  • Resolve the url to an absolute URL - by relative to the entry + relative to the entry script's base - url. Let resolvedUrl be the result of this resolution. -
  • If the url resolution failed, go to the failure step. + URL. Let resolvedUrl be the result of this resolution. +
  • If the URL resolution fails, go to the failure step.
  • Navigate the presentation browsing context to resolvedUrl with the browsing context of the incumbent script as the source browsing context.
  • Success: Fulfil promise with @@ -519,8 +519,8 @@

    8.2

    8.3 Display Availability Changes

    If the display configuration of the user agent's host system changes so that the secondary display is not available - anymore, or if a display connected via the network becomes unreachable, and the user agent was showing an existing - presentation browsing context on the display which is now unavaible, the user agent should follow the regular + any more, or if a display connected via the network becomes unreachable, and the user agent was showing an existing + presentation browsing context on the display which is now unavailable, the user agent should follow the regular algorithm for closing a browsing context.

    @@ -566,7 +566,7 @@

    References

    -

    Acknowledgments

    +

    Acknowledgements

    Thanks to Wayne Carr and Anssi Kostiainen for input, thorough reviews and feedback to this draft.

    From 8e704859d66b1034b74ca6b0530b88c59e8be275 Mon Sep 17 00:00:00 2001 From: Daniel Davis Date: Wed, 2 Jul 2014 17:01:36 +0900 Subject: [PATCH 2/2] Fixed a few typos --- index.html | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/index.html b/index.html index 7e08969..ac9a4e8 100644 --- a/index.html +++ b/index.html @@ -176,7 +176,7 @@

    Table of Contents

  • 8.4 Close on Unload
  • 9 Security Considerations
  • References
    • -
  • Acknowledgments +
  • Acknowledgements

    1 Introduction

    @@ -566,7 +566,7 @@

    References

    -

    Acknowledgements

    +

    Acknowledgements

    Thanks to Wayne Carr and Anssi Kostiainen for input, thorough reviews and feedback to this draft.