Re: [mediacapture-screen-share-extensions] Consider dropping permission for captured surface control APIs (#14)

> A new iframe allow="display-capture https://a.com; captured-surface-control https://a.com;" that web developers need to turn on explicitly

That is desirable. Think embedding a third-party video-conferencing tool into an application and limiting its capabilities to control the user experience.

> A new permissions.query({name: "captured-surface-control"}) value web developers need to consider

That not a problem.

> Implementation-defined behavior web developers need to consider for interop

This point is purely academic, because we deem the permission policy as required, and that means we have to introduce this implementation-defined part of the API (your own citation discusses that the policies are impl-defined). Luckily, we can more easily reach consensus here, because our belief that a permission policy is needed, does not force you to also implement things this way - you are free to infer user intent and skip a prompt.

> One might even say a new permission without good reason is a failure to standardize.

There are good reasons and they have been presented to you in this thread as well as the earlier threads ([[1]](https://github.com/w3c/mediacapture-screen-share-extensions/issues/13), [[2]](https://github.com/screen-share/captured-surface-control/issues/27)).

> I've not heard a good reason yet for this level of granularity at the iframe level, or at the prompt level.

For iframes - see earlier in this comment.
For prompt - you have heard good reasons, please read @steely-glint's [comment](https://github.com/w3c/mediacapture-screen-share-extensions/issues/14#issuecomment-2426657705) and my comments on both this thread as well as the earlier threads ([[1]](https://github.com/w3c/mediacapture-screen-share-extensions/issues/13), [[2]](https://github.com/screen-share/captured-surface-control/issues/27)).

> If there's a way to avoid this extra level of complexity for web developers (not vendors), I'd like to exhaust those ideas first.

The onus is on you to present a way to avoid this "level of complexity".

-- 
GitHub Notification of comment by eladalon1983
Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share-extensions/issues/14#issuecomment-2428600536 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 22 October 2024 08:25:23 UTC