- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Tue, 22 Oct 2024 14:56:49 +0000
- To: public-webrtc-logs@w3.org
> It is not clear to me that this particular permission will be easy to explain to the user In our experience, it does help. But browsers are free to skip the permission prompt. > As an illustration, is it Chrome's plan for this permission to be exposed to website settings pane along location, camera, notification and so on? Yes. > Most of the permissions I saw are high level permissions like camera, location... > ... > Note that this feature is very particular since it is already gated by screen share permission. I do not think other permissions are usually gated by super permissions. PTZ is gated on camera. We have a precedent. > To be noted that it would be convenient for the user/UA to enable/disable/reenable gesture forwarding during a capture. > The current API does not really offer this flexibility. API checks permission at a single place and the web page will then think that forwarding is on until the end of the screen share capture. The spec mandates that every forwarded event is permission-checked before being forwarded. By the way, **you have just made my point for me** - that you want the UA to allow users to revoke this capability, be it during a capture session or outside of one, perfectly illustrates the need for the **established**, **vetted**, **meticulously spec-ed and implemented** mechanism of permissions policies. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share-extensions/issues/14#issuecomment-2429520269 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 14:56:50 UTC