- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Wed, 23 Oct 2024 08:08:21 +0000
- To: public-webrtc-logs@w3.org
> My "slap a permission on it" refers to what you asked other browser vendors to do in https://github.com/w3c/mediacapture-screen-share-extensions/issues/14#issuecomment-2426621419, which you said was "trivial". Thank you very much, but I'd prefer not to take that advice. I think you have misread that comment. Please read it again. It said that you could have a "trivial" implementation that *avoids* a prompt, so it's the opposite of slapping a permission (prompt) - it said it would be "trivial" for you to avoid the permission (prompt). > We'd disable forwarding, not those things. UAs already do all sorts of mitigations like this. So that doesn't seem unusual. 1. It's unclear to me that it's feasible. Determining what draws over what sounds simple, but these are plentiful and complex system, and I suspect it might be infeasible. 2. We have feedback from multiple Web developers saying they use it in exactly the way you seek to block. 3. We have a browser (Chrome) saying they are unwilling to implement it without a permission, whereas other browsers are perfectly able to skip the prompt if they wish, and have the flexibility to change their mind on it multiple times as the years go by and new information pours in. Given these points, I don't see what this discussion aims to achieve. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share-extensions/issues/14#issuecomment-2431236074 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 08:08:22 UTC