- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Oct 2024 14:04:30 +0000
- To: public-webrtc-logs@w3.org
> PTZ is gated on camera. PTZ is not a permission, it is a descriptor. > If you think my example is absurd, consider the value to an attacker of being able to see a couple of slides ahead in an earnings call. The only protection that the Google Chrome prompt will provide is that most users may ignore it. I am not sure they might be able to understand the potential threats, this is pretty hard. If implementing a synchronous prompt in Safari, I am not sure how I would convey the right message to the user. One disconnect seems to be that one approach is to start small and very protective and another approach is to support all potential use-cases. The MVP to me is to forward user gestures for a video element that is fully displayed and without any other element above it. We should further define what we want to address in v1. > * Elad argues is a great example for the benefits of the pre-existing, well-specced and well-implemented Permissions mechanisms. I might have missed my explanation. Revocation is basically page wide, which does not work well since the granularity may be on a per media element basis. That is not to say there are no pros for the permission model or permission policy. picture-in-picture is using it to control third-party delegation. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share-extensions/issues/14#issuecomment-2432319997 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 23 October 2024 14:04:31 UTC