Remote Playback API discovery mechanism requires preloading |
||||||
Issue description<video preload=none></video> or any media element when Data Saver is ON will not notify the page with media.remote.watchAvailability(). The reason is that the WebMediaPlayer isn't created and it is required in order to be notified for remoting routes.
,
Jun 19 2017
I don't think we want to show the cast button for media that uses unsupported codecs and we won't get the codec info until the media is preloaded. We could in theory start preload if we detect user has a Chromecast, but I would not want wasting user's battery by doing a Chromecast search if preload is none / DataSaver is on. Maybe we could do some best effort approach, e.g. if we know there's a Chromecast due to other reasons in Chrome (e.g. some site is using Presentation API or we know this client used Chromecast in the past). The worse alternative would be to show the cast button for any media that's not preloaded and then notify the user it's not supported when the codecs are not compatible on casting. Thoughts are welcome :)
,
Jun 20 2017
Wouldn't the impact of checking for a Chrome Cast when preload=none vs preload=metadata/auto very low. I mean, the user will most likely have encountered other media with other preload values. In the case where we force preload none, that means that we would only check for Chrome Cast visibility when playback starts in which case, maybe that makes sense. I realise my initial message was lacking a use case. The reason why it might be interesting to have is for the case where a webpage wants to have a <video> to play locally and a hidden <video> to use for remote playback. Given that the videos might be different, the website would have good reasons to not preload the hidden video.
,
Jun 20 2017
We do need to preload the video's metadata to be able to detect if it's compatible. Maybe we could treat availability callbacks presence to trigger preload ignoring DataSaver/preload=none if on not on mobile network? (note atm there will always be callbacks set by the controls / overlay cast button)
,
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
Looking into impact.
,
Aug 21
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by sko...@chromium.org
, May 31 2017