W3C home > Mailing lists > Public > public-html-bugzilla@w3.org > October 2013

[Bug 21854] Define MediaKeySession life cycle states and/or events

From: <bugzilla@jessica.w3.org>
Date: Mon, 28 Oct 2013 23:06:14 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-21854-2486-vbwX1TRplp@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=21854

David Dorwin <ddorwin@google.com> changed:

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

--- Comment #23 from David Dorwin <ddorwin@google.com> ---
(In reply to Adrian Bateman [MSFT] from comment #19)
> I added text describing the internal state of the media key session:
> https://dvcs.w3.org/hg/html-media/rev/83629aec22e1

This change added the following text to the update() algorithm:
> If the session is not in the PENDING state, throw an INVALID_STATE_ERR.

I don't think this should be the case. There are probably legitimate reasons
for the application to provide a new message without the session requesting it
(and thus being in the PENDING state) - in other words, in the READY state.

There may even be use cases for calling update() in the CREATED, ERROR, or
CLOSED states.


This change also included the following text describing the new keyready event:
> The media element should not be blocked if encrypted data is encountered associated with the initData used to create the session.

I don’t think we can say this. Output protection or other issues could cause
the key(s) in the session to be unusable and thus for the media element to be
blocked.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Monday, 28 October 2013 23:06:15 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 7 January 2015 16:31:45 UTC