W3C home > Mailing lists > Public > public-html-media@w3.org > February 2018

[encrypted-media] Clarify "accessible" and "asynchonously"

From: mwatson2 via GitHub <sysbot+gh@w3.org>
Date: Fri, 23 Feb 2018 16:33:12 +0000
To: public-html-media@w3.org
Message-ID: <issues.opened-299771244-1519403591-sysbot+gh@w3.org>
mwatson2 has just created a new issue for https://github.com/w3c/encrypted-media:

== Clarify "accessible" and "asynchonously" ==
The specification describes the MediaKeySession lifecycle in terms of whether it is "accessible", based on an original discussion and proposal here: https://www.w3.org/Bugs/Public/show_bug.cgi?id=24771

It may not be clear to readers what this means. I suggest an additional note, after the 4th paragraph of Section 6, as follows:

>         Accessible means that the page maintains a reference to the object, or could obtain one from another object to which it has access (in this case from a Media Element). Therefore, the above requirement means that a <a>MediaKeySession</a> remains active and continues to receive events provided the page maintains a reference to the associated <a>MediaKeys</a> object or a Media Element to which it is attached. If that is not the case, the <a>MediaKeySession</a> could never be used and will not receive further events.

Additionally, this section uses the term "asynchronously" when it should say "in parallel".

Please view or discuss this issue at https://github.com/w3c/encrypted-media/issues/438 using your GitHub account
Received on Friday, 23 February 2018 16:33:14 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 15:49:22 UTC