W3C home > Mailing lists > Public > public-secondscreen@w3.org > May 2016

[remote-playback] [Meta] Guidance for HTMLMediaElement, HTMLAudioElement, HTMLVideoElement behaviors during remoting

From: Mark Foltz via GitHub <sysbot+gh@w3.org>
Date: Fri, 20 May 2016 19:15:16 +0000
To: public-secondscreen@w3.org
Message-ID: <issues.opened-156032232-1463771715-sysbot+gh@w3.org>
mfoltzgoogle has just created a new issue for 
https://github.com/w3c/remote-playback:

== [Meta] Guidance for HTMLMediaElement, HTMLAudioElement, 
HTMLVideoElement behaviors during remoting ==
In remoting mode (i.e. state == `connected`) any side effects on the 
media element, for example mutations to properties, invocations of 
methods, or detachment from the DOM may (or may not) affect remote 
playback.

Because the behavior of the remote playback device seems to be out of 
scope for this spec, there may not be much to say in the normative 
sections of the spec.

However, in my opinion it would be a better spec to at least say 
something in regards to what should happen.  I can see these behaviors
 falling into three categories:

- *Must-implement* for any reasonable experience: e.g, pause, mute, 
stop
- *No-op* as they may not make any sense: e.g., setting autoplay or 
preload during remote playback 
- *Implementation choice* based on the device capabilities and desired
 UX.

The challenge will be in cases where the observable state of the 
element might be affected by implementation choices.  For example,  
when playing back on a remote device that does not support changing 
the playback volume, how should the element behave when its `volume` 
attribute is set?


Please view or discuss this issue at 
https://github.com/w3c/remote-playback/issues/41 using your GitHub 
account
Received on Friday, 20 May 2016 19:15:18 UTC

This archive was generated by hypermail 2.3.1 : Friday, 20 May 2016 19:15:18 UTC