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

[Bug 17750] Define the behavior MediaKeySession close() and clearing the keys attribute

From: <bugzilla@jessica.w3.org>
Date: Tue, 01 Oct 2013 15:00:36 +0000
To: public-html-bugzilla@w3.org
Message-ID: <bug-17750-2486-CI7jdA9QFP@http.www.w3.org/Bugs/Public/>

--- Comment #8 from Adrian Bateman [MSFT] <adrianba@microsoft.com> ---
My proposal for close is as follows (I think this also solves for Mark's
comments in bug 17199):

We should add a new state to the state diagram CLOSED. It is possible to get to
CLOSED from CREATED, PENDING, and READY. A keyclosed event is fired when this
transition occurs.

There are two ways to end up in the CLOSED state:

1) The CDM may have information to know that a session is no longer needed for
anything and can fire keyclosed to notify the application.

2) An application can call the close() method. This may move the session
directly to CLOSED (by causing keyclosed event to fire). In the secure key
release case, a move to PENDING and then CLOSED occurs (with corresponding
keymessage and keyclosed events).

When a session is in the CLOSED state, no further events will be fired. Calling
close() in the CLOSED state is a no-op. CDMs are not required to take any
action related to keys but they may do whatever they want.

You are receiving this mail because:
You are the QA Contact for the bug.
Received on Tuesday, 1 October 2013 15:00:38 UTC

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