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

> PTZ is not a permission, it is a descriptor.

I see [this](https://ff0cc06c87bfc9e916b7037b0537483a8e91ec82341e9525a6570f6-apidata.googleusercontent.com/download/storage/v1/b/chromium-translation-screenshots/o/114f756356148c9d3251d118dc591bec486265cc?jk=AdvOr8vJAcYQnRfZEz0bUnDhMR3sAja45RlIVMeIi6FTmRezcXVODD2VR027J5s409AuCaNPLhJkzlmuhuQmSvsAhlqBiDxlgAo2JvXhEl5kr9GQRyzeSsMjl0gKUBW77fSnE4G_f7iZwsn3ZKD8PSoOSWZjQIMp14OqQ1wY9KetpqIVNxLR5MT0PaIURRNHWCvRtCm7IAd3Bjwz0PdAaYo6kqioKsbXu0Swp9jv8EF4XDmBC0AE-hfUbaZ6IMYn8yiciJASSvdEqbt_ss8BH9Iz3IpgrA3P2sXatRQpjzS4PkCVFr_bpU_eqQBlodf2LXoi3tOwoK1hF6Xv8a7PutVfgt4DrsHJcqfeiXWfeIcccPZWfNWS2pCJV3pasWDreMRNLXNDCeTQHyy9OVmBi8RQw4DPZWJck63G_xGMbrans850S42aYaXhv3W_B99F2GEVr1u9dpikg64CY1LyyK9K-ze66oTrUHAGpIUHPRJAZuD_YBL5NV7RMH081g5rwkgGXMWTXUlXichxvg-uhIaiu_5hYXm7i2-Zz0xFzsmaqo9upmZKr9zhgPSmfSuAVC6hNCfdaYEi3yd4aogkMxF1Mzr1ptYwopm6zKrtN7y8JKUIFkmgAeuupV9qfgfZEcEwIzdJYWvw7UuJUDXr9RMp5jk_ajEznEZBxuDLcu-Y_yG6AE_1Pf0RTGBeNRZzEmYkLGO2glTtem2ATpiz1taB4PLfIIIdf3atwqXaaZj5Bm3Xx1f_DHZFdl4JLpk-5VKiqjM7vVwNm4wkxTi_fciChzgcgc7Gd0M_3aum6Y4FyYMlduffzfzcyn-_BR81_g1ARIoGN6MJbKTMZl33COZHN-XkDLIzZOoeP3Pv_CFk6qKt70obY03bYQzEpYdGdNjjnKngPrMTMAOE94sFXDF7eruh38zEyUhNZ_4wtM6K_bBPyB8K53DMCQxZa7azqZI-6CjHEso2MsPVzLlTrBueBYQvoCxx8vR-gYpACab7Xi_Q-CFnAvc4Jr3alipFlsWE3aZ-RLC5kSwQI_fJhq35WFO6cXXeKSw_vmwNiKiGRvW2vWJriOgWvQQkx2aAuRlyAWawgc9t6w7ymxGvUkjeuFz6eFEakeW9fk8_5ZJVzjVN-AHvl10OI8hNqzYgtsNGLlAijtqSzorV-jP-DTq63oyjcic5oYHLqefLnbgSkuoBsFIzz8lm2omch-_hF90_hBhKEdEfeyj6dtsbfWIq3IYNu1YDwnyg1QpkLYrrkxrJpA7vDKTxb9_oh6MatW5RDP8QBVZQLxj_hAE-eZzhGLgIfGQW7d_mLgYc11GbF3ke3dAjvflmrclWZ0o&isca=1) in Chromium's Translation Console (database of localized strings with some visual context for the translator). Possibly I am missing some later development and/or a nuance?

> The only protection that the Google Chrome prompt will provide is that most users may ignore it.

Nobody has said this would be the only protection. We have already discussed multiple other protections; see the move from `sendWheel()` to `captureWheel()`, for instance.

> If implementing a synchronous prompt in Safari

We are not proposing a synchronous prompt.
Jan-Ivar did ([here](https://github.com/w3c/mediacapture-screen-share-extensions/issues/13#issuecomment-2429352632)), but I objected ([here](https://github.com/w3c/mediacapture-screen-share-extensions/issues/13#issuecomment-2429565114)).

> 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.

If this is about a permission prompt, then starting small is to have it and potentially remove it.
If this is about limiting the element type, then video is too small - we have multiple developers in the origin trial that forward from a non-video element, and I am not aware of any that are forwarding from a video element. It is clear that the MVP includes non-video elements. It is NOT clear what would be gained by limiting to video-elements; the mitigation has been shown, multiple times, to be insufficient to increase security. I dare say - it's theater.

> I might have missed my explanation

I think you mean "you", and if so, then yes, I have missed it. Could you please link me to the relevant comment?

> Revocation is basically page wide, which does not work well since the granularity may be on a per media element basis.

Multiple concurrent screen-captures by one application is an edge-case that I don't expect to tackle in Chrome. (But the spec does not prohibit it, so other browsers should not be bothered.)


-- 
GitHub Notification of comment by eladalon1983
Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share-extensions/issues/14#issuecomment-2432441340 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:36:39 UTC