- From: Anton Vayvod via GitHub <sysbot+gh@w3.org>
- Date: Mon, 20 Mar 2017 00:22:36 +0000
- To: public-secondscreen@w3.org
Ok, revisiting the issue as both APIs are now shipping in Chrome. I'd like the metadata at least to be applied to the remote playback if set on ```navigator```. The actions and event handlers are harder to define though - it doesn't seem like a good experience to pause both local and remote playback, for instance. It would be okay if only remote playback is happening (e.g. on iOS as I remember, remote and local playback are mutually exclusive). Otherwise we could add a separate, per-element [```MediaSession```](https://wicg.github.io/mediasession/#mediasession) object under [```remote```](https://w3c.github.io/remote-playback/#dom-htmlmediaelement-remote) that would override the one set on ```navigator.mediaSession``` if not null. The corresponding issue on the MediaSession spec (closed as it was mostly about audio focus) is [here](https://github.com/WICG/mediasession/issues/123). -- GitHub Notification of comment by avayvod Please view or discuss this issue at https://github.com/w3c/remote-playback/issues/10#issuecomment-287660170 using your GitHub account
Received on Monday, 20 March 2017 00:22:42 UTC