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

Clarifies callbackId requirements. #90

Merged
merged 3 commits into from
Jun 16, 2017

Conversation

markafoltz
Copy link
Contributor

PTAL @avayvod @mounirlamouri

Addresses:

This asserts that the callbackId is unique among all ids assigned for a given browsing context (frame), ensuring that there will be no duplicates in the set of availability callbacks for a given media element, and that Web developers can aggregate callbacks across media elements without worrying about duplicate ids.

Note that calling watchAvailability twice with the same callback object is legal:

  1. It will generate two distinct ids.
  2. It will be invoked twice when availability changes.
  3. It will need to be canceled twice (once with each id).

@avayvod avayvod merged commit 665cbd7 into w3c:gh-pages Jun 16, 2017
@markafoltz markafoltz deleted the issue-85-callback-id branch June 7, 2018 18:19
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants