Re: [w3ctag/design-reviews] Autoplay Detection: async vs sync API (#439)

Hi,

We looked at this issue in our Cupertino F2F. We agree that the Design Principles document needs to be updated to cover nuanced cases like these. We've filed w3ctag/design-principles#145 to track that update.

We think, in this case, **the API should be synchronous**, due to many factors that have already been captured in the minutes of the Media WG session at Fukuoka, and in our minutes today (which I will link here once they're posted), namely:

* An async API would unnecessarily complicate the work of web developers (and while this may enable particular implementation strategies, the [Priority of Constituencies](https://www.w3.org/TR/html-design-principles/#priority-of-constituencies) favors web developers over browser engineers),
* A sync API is more predictable and would not have timing issues (such as when you create a promise during a user gesture and resolve it outside of that gesture).

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/439#issuecomment-561902607