- From: Mounir Lamouri via GitHub <sysbot+gh@w3.org>
- Date: Mon, 20 Mar 2017 09:59:42 +0000
- To: public-secondscreen@w3.org
One principle of the Media Session specification is that the instance on `navigator.mediaSession` will hook itself to the default audio focus used by the user agent. With remote playback, the user agent uses a different audio focus than the one on the device which means that handling remote playback in the default media session would break this principle. Adding a `MediaSession` instance on the `media.remote` instance can help but it sounds slightly limited as other things could benefit from a "remote" media session. I don't have any good idea though. The only thing I can think of is to allow a `remote` audio focus (when the Audio Focus API happens) that could receive a media session. Though, I am not sure how useful the remote audio focus would be apart from linking to the media session. -- GitHub Notification of comment by mounirlamouri Please view or discuss this issue at https://github.com/w3c/remote-playback/issues/10#issuecomment-287716307 using your GitHub account
Received on Monday, 20 March 2017 09:59:50 UTC