Skip to content

Commit

Permalink
Merge pull request #302 from w3c/fix-spec
Browse files Browse the repository at this point in the history
Attempt to fix the spec.
  • Loading branch information
markafoltz authored Oct 18, 2022
2 parents c2d4001 + 42124c3 commit 37cef31
Showing 1 changed file with 11 additions and 13 deletions.
24 changes: 11 additions & 13 deletions index.bs
Original file line number Diff line number Diff line change
Expand Up @@ -23,15 +23,13 @@ urlPrefix: https://html.spec.whatwg.org/multipage/media.html#; type: dfn; spec:
text: official playback position
text: poster frame
text: timeline offset
urlPrefix: https://w3c.github.io/presentation-api/#dfn-; type: dfn; spec: PRESENTATION-API
urlPrefix: https://www.w3.org/TR/presentation-api/#dfn-; type: dfn; spec: PRESENTATION-API
text: available presentation display
text: controlling user agent
text: presentation
text: presentation id
text: presentation request url
text: receiving user agent
urlPrefix: https://w3c.github.io/presentation-api/; type: interface; spec: PRESENTATION-API
text: PresentationConnection
urlPrefix: https://w3c.github.io/remote-playback/#dfn-; type: dfn; spec: REMOTE-PLAYBACK
text: availability sources set
text: compatible remote playback device
Expand Down Expand Up @@ -782,8 +780,8 @@ values:

: headers
:: headers that the receiver should use to fetch the presentation URL. For example,
[[PRESENTATION-API#establishing-a-presentation-connection|section 6.6.1]] of
the Presentation API says that the Accept-Language header should be
[[PRESENTATION-API#creating-a-receiving-browsing-context|section 6.6.1]] of
the Presentation API says that the HTTP `Accept-Language` header should be
provided.

The presentation ID must follow the restrictions defined by
Expand Down Expand Up @@ -1399,13 +1397,13 @@ changed.
: loading
:: The state of network activity for loading the [=media resource=]. See
{{HTMLMediaElement/networkState|HTMLMediaElement.networkState}}.
The default is empty ({{NETWORK_EMPTY}}
The default is empty ({{NETWORK_EMPTY}})
for the initial state in the [=remote-playback-start-response=] message.

: loaded
:: The state of the loaded media (whether enough is loaded to play). See
{{HTMLMediaElement/readyState|HTMLMediaElement.readyState}}.
The default is nothing ({{HAVE_NOTHING}}
The default is nothing ({{HAVE_NOTHING}})
for the initial state in the [=remote-playback-start-response=] message.

: error
Expand Down Expand Up @@ -1581,10 +1579,10 @@ This is how the [[REMOTE-PLAYBACK|Remote Playback API]] uses the
messages defined in [[#remote-playback-protocol]]:

When [[REMOTE-PLAYBACK#the-list-of-available-remote-playback-devices|section
6.2.1.2]] says "This list contains [=remote playback devices=] and is populated
5.2.1.2]] says "This list contains [=remote playback devices=] and is populated
based on an implementation specific discovery mechanism" and
[[REMOTE-PLAYBACK#the-list-of-available-remote-playback-devices|section
6.2.1.4]] says "Retrieve available remote playback devices (using an
5.2.1.4]] says "Retrieve available remote playback devices (using an
implementation specific mechanism)", the user agent may use the mDNS, QUIC,
[=agent-info-request=], and [=remote-playback-availability-request=] messages
defined previously in this spec to discover [=receivers=]. The
Expand All @@ -1593,7 +1591,7 @@ sources set=].

When
[[REMOTE-PLAYBACK#establishing-a-connection-with-a-remote-playback-device|section
6.2.4]] says "Request connection of remote to device. The implementation of this
5.2.4]] says "Request connection of remote to device. The implementation of this
step is specific to the user agent." and "Synchronize the current media element
state with the remote playback state", the controller may send the
[=remote-playback-start-request=] message to the receiver to start remote
Expand All @@ -1604,7 +1602,7 @@ of [[REMOTE-PLAYBACK|Remote Playback API]] may allow for several.

When
[[REMOTE-PLAYBACK#establishing-a-connection-with-a-remote-playback-device|section
6.2.4]] says "The mechanism that is used to connect the user agent with the
5.2.4]] says "The mechanism that is used to connect the user agent with the
remote playback device and play the remote playback source is an implementation
choice of the user agent. The connection will likely have to provide a two-way
messaging abstraction capable of carrying media commands to the remote playback
Expand All @@ -1616,8 +1614,8 @@ based on changes to the local media element and receive
change the local media element based on changes to the remote playback state.

When
[[REMOTE-PLAYBACK#establishing-a-connection-with-a-remote-playback-device|section
6.2.7]] says "Request disconnection of remote from the device. The
[[REMOTE-PLAYBACK#disconnecting-from-a-remote-playback-device|section
5.2.7]] says "Request disconnection of remote from the device. The
implementation of this step is specific to the user agent," the controller may
send the [=remote-playback-termination-request=] message to the receiver.

Expand Down

0 comments on commit 37cef31

Please sign in to comment.