Use MediaSession's metadata for remote playback |
||||||
Issue descriptionIt's not trivial but it seems unintuitive that if the user plays a media element locally, the notification shows web site provided data while in the remote case it's still the inferred data. The tricky part is associating the metadata from the media session object that lives off navigator to the remoted media element :/ I think we could either use the metadata as long as there's no local playback simultaneously (so we only show one notification - for remote playback) or use it for both notifications maybe? Note that the metadata in the remote case is typically shown on the remote playback device too. Otherwise it might be overdue to think about the RemotePlayback and MediaSession API integration issues: - https://github.com/WICG/mediasession/issues/123 (could be reopened) - https://github.com/w3c/remote-playback/issues/10 Maybe add v.remote.mediaSession that would override navigator.mediaSession if not null? (let's continue the discussion in one of the issues above though)
,
Mar 20 2017
Assigned to you avayvod@ for tracking.
,
May 31 2017
,
Jul 16 2017
Bump on this issue! I have this little app - totally not prod ready; https://sverige-science.firebaseapp.com/#!/podcasts?show=historiepodden I play around with media session here, and thus image and metadata is displayed on lock screen / notification in Android. But when a user clicks the "Cast" button; the metadata from MediaSession is not sent to the cast session. I assume that goes under this issue; so I'll refrain from making a new one. :)
,
Jul 17 2017
enjikaka@gmail.com: Can you provide explicit steps to start casting from your site? I don't see a Cast icon, and when I clicked a "play" button at the URL provided nothing happened. (This was on Chrome on Mac OS X).
,
Jul 18 2017
You did the right steps. The cast button is in the <audio> tag. But you must be on Chrome on Android connected to WiFi which has a cast device in it for the icon to appear in the audio tag. Den mån 17 juli 2017 22:26mfo… via monorail < monorail+v2.546831754@chromium.org> skrev:
,
Jul 18 2017
Clicking the play button should reveal an audio tag. It might be out of viewport initially, so you might have to scroll down to it. (This is because I have not tweaked the layout for anything other than viewing in the PWA launched from homescreen yet, so the chrome toolbar pushes it down). Den tis 18 juli 2017 13:50Jeremy Karlsson <enjikaka@gmail.com> skrev:
,
Jul 24 2017
mfo...@chromium.org: Oh sorry, my cache tricked me, so I deployed a version without working playback. It should be fixed now. Make sure you clear the cache and possible the service worker too and it should work again. Sorry for the bug. If you don't get it to work, please tell; then I can make an isolated test on Codepen or something on the issue for you, so you can test.
,
Aug 14 2017
,
Aug 15
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 21
Need to evaluate whether this still repros. |
||||||
►
Sign in to add a comment |
||||||
Comment 1 by avayvod@chromium.org
, Mar 20 2017