[Bug 26776] Diagnosing and resolving CDM errors needs a numeric systemCode (deleted with MediaKeyError)

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

--- Comment #11 from Mark Watson <watsonm@netflix.com> ---
(In reply to David Dorwin from comment #10)
> As discussed at TPAC, there are two issues:
> 1) Should we expose key-system specific values in a way that applications
> could switch on? (And how can we prevent/discourage that?)

No, client applications should not switch on key-system specific values - they
should be for reporting to the server for offline error analysis only.

Not sure what we can do except say that applications should not switch on
these, they might change etc.

> 2) If so, how should we expose them?

And if not, how should we expose them ;-)

 "Errors" related to EME can include
> HTMLMediaElement decode errors (MEDIA_ERR_DECODE), rejected promises, and
> unusable keys (bug 26372). If system codes apply to all, how should we
> report them. One argument is that any EME-related error that might cause
> playback to stop probably results in a key not being usable. Thus, the
> solution for the first category might be reported via the last one.
> 
> Jerry to drive resolution for #1 then propose something for #2.

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

Received on Monday, 3 November 2014 17:25:39 UTC