- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Fri, 18 Jun 2021 00:09:12 +0000
- To: public-webrtc-logs@w3.org
> Again, cropping is not a security guarantee, so no, they're not approving only the cropped area. I beg you to read my messages more carefully. The user approves the entire tab. I've been arguing that very point all along. Like [here](https://github.com/w3c/mediacapture-screen-share/issues/158#issuecomment-863338821): "The end-user consents to capturing the entire tab, always." If you think this is not clear enough, I am always eager to hear how I can enhance the clarity of my writing. > (Crbug 2276 aside) how would one implement only a non-default value web-compatibly? By raising an exception, either compatibly or incompatibly. But that is not the best way forward. It would be better to align our visions: I do not consider cropping to the current iframe an important case, but I do consider cropping to an arbitrary iframe important. One is a subcase of the other. If we specify some support for cropping to an arbitrary iframe, then Chrome will implement that ability relatively soon. It will then be trivial to support "self" as well. That means no risk of a gap between specification and implementation; no compatibility issues; **no problem setting "self" as the default value**. A good compromise, I believe. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/158#issuecomment-863638133 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 18 June 2021 00:10:11 UTC