Use Media Session API in the Media Document |
||||
Issue descriptionGoogle Search App handles podcasts very well and even shows "seek backwards" and "seek forward" buttons in their notifications: go/gsa-podcast I believe Chrome should do the same for audio only media and even copy seek time values: - "Seek backward" time is 10s - "Seek forward" time is 30s We may want to not apply this to LIVE audio streams yet though.
,
Oct 17 2017
I would prefer if websites could use the Media Session API instead of us implementing seeking for them. Even if the issue might be less obvious with audio-only, seeking can create a new type of bugs. We are already running into issues with websites that misbehave when we play/pause them (like NPR).
,
Oct 17 2017
How about adding default seek buttons for audio elements only with native controls? This would be quite useful for people who download podcast files and listen to them while being offline (Think NBU)
,
Nov 6 2017
I wonder if one way to solve this would be to use the Media Session API in our default media player? That should be doable and would improve offline user experience. +dahlke@ as PM for media experience and downloads.
,
Nov 6 2017
when you say "default media player," do you mean the one we use with downloads, or do you mean any media that uses the native media controls?
,
Nov 7 2017
Sorry for the imprecision. I meant the media player we use for downloads and local playback.
,
Nov 7 2017
Yes, I agree. Adding downloads component and marking as untriaged to deal with this in our standard triage session.
,
Nov 7 2017
FWIW, I think the media experience team can take this as we would want this to be the default experience when using MediaDocument anyways.
,
Nov 7 2017
SGTM
,
Nov 8 2017
|
||||
►
Sign in to add a comment |
||||
Comment 1 by beccahughes@chromium.org
, Sep 14 2017