- From: <bugzilla@jessica.w3.org>
- Date: Wed, 15 Oct 2014 23:36:14 +0000
- To: public-html-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=27067 --- Comment #5 from Glenn Adams <glenn@skynav.com> --- (In reply to David Dorwin from comment #4) > This might be better phrased as "when the CDM fails or becomes > unresponsive." Since the CDM is a separate entity in the spec and many > implementations, this could be a real possibility. This should also cover > cases where the "context" is lost, such as on some mobile platforms when the > device goes to sleep. > > For contrast/comparison: The HTML5 spec does not way what to do when a > hardware video decoder fails, but there is a generic mechanism for reporting > decode errors: > MEDIA_ERR_DECODE (numeric value 3) > An error of some description occurred while decoding the media resource, > after the resource was established to be usable. > > We may want to identify a similar mechanism. For example, maybe the first > paragraph of the Session Close algorithm section should be broadened. The > Encrypted Block Encountered algorithm should already cover the behavior > resulting from the keys being unavailable. that sounds reasonable -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Wednesday, 15 October 2014 23:36:16 UTC