- From: <bugzilla@jessica.w3.org>
- Date: Wed, 17 Sep 2014 17:04:52 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26372 --- Comment #19 from Joe Steele <steele@adobe.com> --- I propose something between #1 and #2. Let's create a keystatus event which includes a status enum, a key ID and a system code. The CDM would send this event any time a keys status enum changes. This would supersede keyschange and getUsableKeyIds(). Pro - * Easy to consume on the app side * More flexible for apps * Easier to implement for browsers/CDMs Con - * App has to track all such events if it cares * App has to maintain state structure if it cares * Key statuses might overlap with other errors? I suggest the following enum values: "acquired", "expired", "notyetvalid", "renewalfailed", "playbacksexceeded", "authorizationfailed", "outputnotallowed", "downscaling", "released" -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 17 September 2014 17:04:58 UTC