Failed or unsupported playback UX for default controls needs some work. |
|||||||||
Issue descriptionToday a failed playback using default controls just grays out the playback control, this isn't very clear to users. See samples like: http://storage.googleapis.com/dalecurtis/broken.mp4 (bad file) http://storage.googleapis.com/dalecurtis/broken_mpeg4.mp4 (unsupported codec on desktop/android platforms). Instead of graying out the play button we should display something more informative and possibly even ask the user if they'd prefer to download and try to playback the media locally. Downloading may require some security discussions. For reference here are what some other players do: YouTube: https://www.youtube.com/watch?v=xDAaa5ViYMo Vimeo: http://stackoverflow.com/questions/23607204/vimeo-embedded-video-cannot-be-played-in-firefox/31518200 Netflix: http://www.hawkdive.com/2015/11/fix-hdcp-compliant-display-error-when.html
,
Sep 14 2016
Doing this for <audio controls> might be challenging :)
,
Oct 4 2016
,
Nov 3 2016
,
Dec 7 2016
Issue 669943 has been merged into this issue.
,
Jun 30 2017
Is there still intent to address this bug?
,
Jul 17 2017
Yes, assigning to me to figure that out.
,
Sep 7 2017
Any update on this Jon? I just got pinged about this on issue 763156.
,
Sep 7 2017
Thanks for the ping. +rachelis@ and amyroberts@ to think about for the native controls spec. At minimum, we should tell the user we can't play back the video. It would also be good to think about a send-feedback button for when that happens. dalecurtis@ do we have user-friendly error messages? If not, would any sort of error code or other diagnostics info be shown as part of the screenshot for send-feedback? hbengali@ Do we have data on how often playback failure occurs and why?
,
Sep 7 2017
I think any of the examples in my original post would be good. To avoid having to localize all the strings we can reuse whatever wording YouTube has and maybe badge it with some kind of sad tab icon.
,
Sep 8 2017
Thanks folks. Would you mind helping me understand the size of this problem, for prioritization? How often are users seeing these errors?
,
Sep 9 2017
According to our pipeline status UMA metric [1], around 2% of playbacks have something other than a pipeline OK status. I am not clear if each of those would result in this message - dalecurtis@, can you clarify which pipeline status messages would lead to the error above? [1] https://uma.googleplex.com/p/chrome/timeline_v2?sid=4ee4ec4551a518d90277fd5f7063429d
,
Sep 9 2017
Yes, anything other than PIPELINE_OK is an error. Presumably if native controls are being used we can show a sad tab error then. Possibly we want to do something even when custom controls are shown, but not sure.
,
Jan 12 2018
Issue 799494 has been merged into this issue.
,
Feb 6 2018
|
|||||||||
►
Sign in to add a comment |
|||||||||
Comment 1 by dalecur...@chromium.org
, Sep 12 2016