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

Intent to Migrate: Autoplay Policy Detection #9

Closed
tidoust opened this issue Jul 9, 2019 · 3 comments
Closed

Intent to Migrate: Autoplay Policy Detection #9

tidoust opened this issue Jul 9, 2019 · 3 comments
Assignees

Comments

@tidoust
Copy link
Member

tidoust commented Jul 9, 2019

Intent to Migrate: Autoplay Policy Detection

Hi all, cc @mounirlamouri @jernoble as chairs of the Media Working Group. The recently created Media Working Group is ready to adopt Autoplay Policy Detection as a W3C Recommendation track deliverable.

Note some of the sections below need some love. I let people involved in the development of this proposal chime in as needed!

Working group decision to adopt

See the charter of the Media Working Group

Proposal

The API design is still at early stage, described in GitHub issues for now.

Summary

An API to allow websites to determine the document-level autoplay policy and whether autoplay will succeed for a given media element in a page.

Motivation and Use Cases

See notes of informal meeting at TPAC 2018 and proposed explainer

Compatibility Risk

Please characterize how much we might regret standardizing this new feature were we to change or remove it in the future. If you don’t have a github repository, include in this email links to relevant discussions, or documentation about support for the feature on the Web.

Ongoing technical constraints

The API exposes information that user agents already know, and the API is read-only, so technical constraints for implementing the API should be minimal.

It is expected that all environments will support this feature.

Link to implementation experience and demos

If your proposal has implementation experience or demos, please provide links, including common patterns in deployed libraries. Otherwise, indicate if there are none.

Data

What data do you have available that indicates that this enhancement will affect many users of the Web. Quantify the fraction of websites that are currently using something similar to this feature. Or, if a new feature, characterize the reason that you expect this to be far reaching.

Security and Privacy

To be evaluated. The API exposes information that applications can already determine through a trial and error approach.

Accessibility

This proposal should have no accessibility implications.

Internationalization

This proposal should have no internationalization implications.

@marcoscaceres
Copy link
Member

this intent to migrate seems ok, though we should give people until the 17th of July to provide any additional feedback.

@marcoscaceres
Copy link
Member

@tidoust, all, thanks again for preparing the intent to migrate. Kindly please move this over to the Media WG at your convenience.

Just as reminder, once moved, the various bits of spec metadata that reference WICG will need changing.

@tidoust
Copy link
Member Author

tidoust commented Jul 24, 2019

Thanks @marcoscaceres, repository has now been transferred to W3C and all relevant info should have been updated. I'm closing the issue accordingly.

@tidoust tidoust closed this as completed Jul 24, 2019
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

No branches or pull requests

2 participants