[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

--- Comment #6 from David Dorwin <ddorwin@google.com> ---
Summary of the discussion in the March 12th telecon:

* joesteele: I see this as a network stall not a decoder stall. Main issue -
what is the time period before something else happens.
markw: if you don't have
the key you don't know how long it will take to get the key (could be seconds)
so this is more similar to network stall. For decoding you know you're going to
do this soon. As a user i probably don't care whether it is network or key
blocking.
* ddorwin: I separate it from network stall because we have the data, we've
de-muxed it, and we're trying to decrypt. Between de-muxing and decoding we
know we have a problem with a key
* markw: The behaviour on the API surface seem most similar to network stall
regardless of how it gets surfaced. We could describe it as "just like a
network stall" or with more detailed steps but the behaviour should be the
same.

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

Received on Tuesday, 23 April 2013 18:06:56 UTC