[Bug 26372] Report issues/events not related to a specific method call

https://www.w3.org/Bugs/Public/show_bug.cgi?id=26372

--- Comment #12 from David Dorwin <ddorwin@google.com> ---
(In reply to Joe Steele from comment #11)
> (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. 

There is no real indication of which key caused the problem, and I do not think
it is guaranteed that an application could determine this in all cases (i.e.
multiple successive events).

> Do we think there are cases where knowing which key caused the error is
> relevant?

We have never had such a capability, so I do not think we would be losing
anything.

> 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).

That would potentially address bug 25092.

However, it would imply that downscaling means that a key is "not usable",
which could be confusing since the CDM is actually using it for decryption.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Tuesday, 2 September 2014 23:10:55 UTC