Playback hangs of Widevine protected content if monitor doesn't support HDCP
Reported by
rik.sa...@vudu.corp-partner.google.com,
May 26 2017
|
||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:53.0) Gecko/20100101 Firefox/53.0 Steps to reproduce the problem: 1. Connect HDMI or DVI monitor to windows laptop or mac laptop 2. attempt to playback Widevine protected content, where the output protection on the content requires output protection What is the expected behavior? The video element must generate an error, to notify that playback is not supported. What went wrong? The video element fires the canplay event. The video element does not report an error and does not start playback. The video element does not start playback (which is OK) Did this work before? No Does this work in other browsers? Yes Chrome version: Version 58.0.3029.110 (64-bit) Channel: n/a OS Version: 6.3 Flash Version: Shockwave Flash 23.0 r0 when attempting playback back (PC or Mac) when the attached monitor doesn't support HDCP. What I see is that the playback simply doesn’t start - there is no error generated. The Video Element gets as far as firing the canplay event, but refuses to start playback. If I remove the cable to the non-HDCP monitor the playback immediately starts. For Chromecast you added canDisplayType(), and we use that to check capabilities before attempting playback. Is there something similar (custom API) on Chrome on desktop? Alternatively, generating a playback error would work. MS Edge browser does the latter. IIRC, their video element throws a DECODE or UNSUPPORTED error. Regards, Rik.
,
May 30 2017
In this case, I think their player should get a keystatus change event, and the player should see "output-restricted" keys. Then if they have "HDCP required" in their policy, the player should know that the content cannot play, and should switch to other streams that does not require HDCP. This is how things should work today. APIs like canDisplayType() are not spec-compliant. And the current HTML5 spec and EME do not specify that the video element should generate an error in this case. Moving forward, we are working on adding early HDCP detection in the EME APIs. The current proposal/explainer is at: https://github.com/WICG/media-capabilities/blob/master/eme-extension-policy-check.md |
||
►
Sign in to add a comment |
||
Comment 1 by ligim...@chromium.org
, May 30 2017