Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Clarify "accessible" and "asynchonously" #438

Open
mwatson2 opened this issue Feb 23, 2018 · 0 comments
Open

Clarify "accessible" and "asynchonously" #438

mwatson2 opened this issue Feb 23, 2018 · 0 comments
Labels
Milestone

Comments

@mwatson2
Copy link
Contributor

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".

@joeyparrish joeyparrish added the bug label Sep 8, 2020
@joeyparrish joeyparrish modified the milestones: V2, V2-Bugfixes Sep 8, 2020
@joeyparrish joeyparrish modified the milestones: V2-Bugfixes, V3 Mar 22, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants