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.

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

Updated media commands section to use normative assertions #32

Merged
merged 1 commit into from
May 17, 2016

Conversation

tidoust
Copy link
Member

@tidoust tidoust commented May 17, 2016

The "Media commands and media playback state" section describe the interaction between the HTMLMediaElement interface and the remotely played media without being very explicit as to what user agents are to be doing.

I updated the section to use "the user agent MUST" sentences.

More discussion might be needed to complete this section. For instance, I assume that the remote media will start in the same state as the local one (e.g. playing at 5.4s), but I don't see that very clearly in the spec right now.

Also, do we expect all media commands to be supported by the remote playback device? (setting "playbackRate" for instance). If not, what is to happen when the application issues such commands?

The "Media commands and media playback state" section described the interaction
between the HTMLMediaElement interface and the remotely played media without
being very explicit as to what user agents were to be doing.

I updated the section to use "the user agent MUST" sentences and e.g. to
reference the "stop remote playback" algorithm.
@avayvod
Copy link
Contributor

avayvod commented May 17, 2016

Some of your questions are asked in issue #25. I agree we need to expand about how each item of the HTMLMediaElement interface works when in the "connected" state allowing enough flexibility for various ways of implementing remote playback (flinging vs remoting vs mirroring)

I really hope for @foolip's help here :)

@avayvod avayvod merged commit c7c4109 into w3c:gh-pages May 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants