- From: Travis Leithead <notifications@github.com>
- Date: Wed, 27 Sep 2017 06:13:35 -0700
- To: w3ctag/design-reviews <design-reviews@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Wednesday, 27 September 2017 13:14:45 UTC
Discussed in F2F in Nice. Thanks for bringing this to our attention! It caused us quite a discussion about auto-play in general :-). The more we discussed this, the more that this "gesture"/"activation" seemed to be a permission-in-disguise. As with permissions, the UA can have a particular policy in place and the [Permissions API](https://w3c.github.io/permissions/) can reflect that status. (We'll spin up another issue for the TAG to consider for something like a Permission Observer...) Given this thinking about auto-play-as-a-permission, we considered this spec. We were pretty united in the desire to see the API shape adopted into [Feature Policy](https://wicg.github.io/feature-policy/). For example, the parent has a permission (policy) applied for the 'autoplay of 'media' [probably blocked by default], and frames are just disallowed until the feature policy is "delegated" using the mechanism there: `iframeOb.allow.add('autoplay-media')` (which is pretty close to the syntax you were already proposing). [Naming subject to change of course.] -- 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/199#issuecomment-332516158
Received on Wednesday, 27 September 2017 13:14:45 UTC