Inspired by conversation in #199, we have noted that the heuristics being implemented by [Chrome](https://developers.google.com/web/updates/2017/09/autoplay-policy-changes) and [Safari](https://webkit.org/blog/7734/auto-play-policy-changes-for-macos/) around auto-playing media with sound are creating a situation where sites may need to "earn" the ability to auto-play. This sounds very much like the sort of asynchronous decision made by the [Progressive Web App install prompt](https://developers.google.com/web/fundamentals/app-install-banners/) system in various browsers and interventions being considered for permissions which are being pervasively requested at load time (but without user interaction). In these cases, it seems as though browsers will always intervene on behalf of users. Developers will struggle to understand the situation until the reflection APIs get better. One possible alternative would be to model auto-playing media within the Permissions API which [already includes a notification mechanism](https://w3c.github.io/permissions/#status-of-a-permission) to let developers know when browsers change the status of a permission. It may be necessary to extend the `PermissionState` enum to handle this situation. /cc @owencm @jyasskin -- 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/203
Received on Wednesday, 27 September 2017 13:11:22 UTC