[Bug 18515] Provide more details on behavior of the media element when the key for an encrypted block is not available

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

David Dorwin <ddorwin@google.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|RESOLVED                    |REOPENED
         Resolution|FIXED                       |---

--- Comment #23 from David Dorwin <ddorwin@google.com> ---
Thanks for adding the proposal to the spec - this makes it easier to discuss.
My comments are below.

* The intent of the following text is unclear - and perhaps unnecessary given
the paragraph above it.
"It is possible for a media element to be playing media and encounter content
that requires decryption keys. To accommodate changes caused by key status,"
* The text following it is written like an algorithm, but each item probably
belongs in a different algorithm.
  - Some of them probably belong in the main Encrypted Block Encountered and
update() algorithms. The former definitely needs to be updated.
  - The rest might be added to any algorithm that fires a "canplay" event.
  - The meaning of each "waitingFor" value and its possible transitions may be
useful, but that is probably better done in a non-normative table like the
Event Summary.
* In bug 24368, I proposed adding something like ", and suspend playback" to
the end of the sentence where a simple event named waiting is fired. I see the
other suggestion was adopted, so maybe this was an oversight.

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

Received on Monday, 24 March 2014 22:23:19 UTC