- From: <bugzilla@jessica.w3.org>
- Date: Fri, 07 Mar 2014 19:26:24 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24874 --- Comment #1 from David Dorwin <ddorwin@google.com> --- On a related note, we should specify what happens when: A) video.setMediaKeys() is called and video.src is already set to a source that does not support EME. B) An attempt is made to set video.src to a source that does not support EME when video.mediaKeys is already set. For (A), we should probably add a step to the setMediaKeys() algorithm that throws NOT_SUPPORTED_ERR or INVALID_ACCESS_ERR if the user agent knows that the media loaded cannot be decrypted/used with EME. For (B), I believe we would need to update the media element load algorithm [1]. However, this algorithm, nor many media element algorithms, throw exceptions. Alternatively, we could just let things fail elsewhere. That's probably more acceptable if there is a clear way for applications to detect incompatibility (like #3 above). [1] http://www.w3.org/TR/html5/embedded-content-0.html#media-element-load-algorithm -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 7 March 2014 19:26:25 UTC