Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Allow remote playback device to choose the remote playback source. #141

Merged
merged 4 commits into from
Nov 10, 2020
Merged

Allow remote playback device to choose the remote playback source. #141

Changes from 2 commits
Commits
Show all changes
4 commits
Select commit Hold shift + click to select a range
5affa86
Allow remote playback device to choose the remote playback source.
markafoltz Oct 14, 2020
2543a1e
Respond to comments from baylesj
markafoltz Oct 15, 2020
3b9ab83
Update per mlamouri comment. Move note.
markafoltz Nov 4, 2020
852e47e
Rewrap
markafoltz Nov 5, 2020
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
63 changes: 33 additions & 30 deletions index.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -571,24 +571,28 @@ <h5>
<dfn>availability sources set</dfn>.
</p>
<p>
The <a data-cite="HTML#media-resource">media resource</a>
of a <a>media element</a>, that is used to
<a>initiate remote playback</a> on the selected <a>remote
playback device</a> is called <dfn>remote playback source</dfn>.
Remote playback source MUST belong to <a>availability sources
The <a data-cite="HTML#media-resource">media resource</a> of
a <a>media element</a> that is used to <a>initiate remote
playback</a> on the selected <a>remote playback device</a> is
called the <dfn>remote playback source</dfn>. A remote playback
source MUST belong to the media element's <a>availability sources
set</a>.
</p>
<p>
The mechanism of picking the <a>availability sources set</a> and
the <a>remote playback source</a> is implementation-specific. For
example, the user agent MUST either use the
{{HTMLMediaElement/currentSrc}} of the <a>media element</a>
for both availability monitoring and remote playback or use all the
<a data-cite="HTML#media-resource">media resources</a>
associated with the <a>media element</a> as the
<a>availability sources set</a> and pick one of the resources as
the <a>remote playback source</a> after user selects the
<a>remote playback device</a>.
The mechanism to choose the <a>remote playback source</a> from
the <a>availability sources set</a> is implementation-specific,
but the user agent SHOULD consider every resource in
the <a>availability sources set</a> as a potential <a>remote
playback source</a>.
</p>
<p class="note">
markafoltz marked this conversation as resolved.
Show resolved Hide resolved
The user agent may send metadata (for example,
the <a data-cite="HTML#attr-source-type">extended MIME type</a>)
about all resources in the <a>availability sources set</a> to
the <a>remote playback device</a> so it can run its own
<a data-cite="HTML#concept-media-load-algorithm">resource
selection algorithm</a> and choose the <a>remote playback
source</a>.
</p>
<p>
Remote playback is said to be <dfn>unavailable</dfn> for the
Expand Down Expand Up @@ -1131,25 +1135,24 @@ <h4>
"RemotePlaybackState">connected</a> through an icon or other means.
</p>
<div class="note">
The mechanism that is used to connect the user agent with the
<a>remote playback device</a> and play the <a>remote playback
source</a> 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 device and receiving media playback state in order to keep
the <a>media element state</a> and <a>remote playback state</a> in
sync (unless <a>media mirroring</a> is used).
The mechanisms that are used to connect the user agent with the
markafoltz marked this conversation as resolved.
Show resolved Hide resolved
<a>remote playback device</a>, select the <a>remote playback
source</a>, and initiate playback are all implementation choices 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 device and receiving media playback state in order
to keep the <a>media element state</a> and <a>remote playback
state</a> in sync (unless <a>media mirroring</a> is used).
</div>
<div class="note">
The user agent is encouraged to pass locale and text direction
information to the <a>remote playback device</a> when possible, so
that the <a>remote playback device</a> can adjust its user
interface and operational functions to locale-specific attributes
that reflect the user's preferences. For example, the <a>remote
playback device</a> can use that information to choose the same
default text track as the user agent, as well as to set the HTTP
`Accept-Language` header it sends to fetch media
resources.
that the <a>remote playback device</a> can adjust its user interface
and operational functions to locale-specific attributes that reflect
the user's preferences. For example, the <a>remote playback
device</a> can use that information to choose the same default text
track as the user agent, as well as to set the HTTP
`Accept-Language` header it sends to fetch media resources.
</div>
<div class="note">
The user agent should not render output from the media element while
Expand Down