- From: <bugzilla@jessica.w3.org>
- Date: Tue, 02 Sep 2014 22:44:33 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26372 --- Comment #11 from Joe Steele <steele@adobe.com> --- (In reply to David Dorwin from comment #10) > Since the remaining events (key availability / valid window, output > protection) affect the usable keys, we could add a reason enum to the > "keyschange" event (it would become a custom event instead of a simple > event). > > Playback issues are already handled by HTMLMediaElement. That leaves key > issues as the only remaining types of issues for MediaKeySession (MediaKeys) > to handle. Since an issue with the key will result in it being unusable, it > makes sense to report this along with the "keyschange" event. (If a > different license has the same key ID and it is usable, there is no reason > to report anything.) This sounds like it would conflict with the current definition of the getUsableKeyIds() method, section 3.2.1. "usable key ids must not contain IDs for keys that may not currently be usable.". Those keys which are not usable due to an error would presumably not be in the list, so it would be up to the application to figure out which key caused the error the reason refers to. Do we think there are cases where knowing which key caused the error is relevant? Assuming the answer is no, this sounds reasonable to me. I would like to include "downscaling" as one of the options (perhaps as a subset of output protection). -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Tuesday, 2 September 2014 22:44:35 UTC