- From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
- Date: Thu, 17 Jun 2021 19:40:33 +0000
- To: public-webrtc-logs@w3.org
> Or better yet - don't allow a default. Force the application to be explicit. Wdyt? That's redundant unless the caller is in an iframe. I'd want the default to be "self" if we go with an option. > as this gives a clear indication of what the user approves [Again](https://github.com/w3c/mediacapture-screen-share/issues/158#issuecomment-862889108), cropping is not a security guarantee, so no, they're not approving only the cropped area. > (Not a critical point for me, but otherwise we might get into a situation where initially, some browsers only supports the less technically-challenging non-default version, and nobody benefits from that.) ([Crbug 2276](https://bugs.chromium.org/p/webrtc/issues/detail?id=2276) aside) how would one implement only a non-default value web-compatibly? > it becomes surprising to users what is actually being captured Sorry I meant web-developer here, not user. My bad. > I see cropping to an arbitrary iframe (not node) as a use-case of utmost importance. Good we agree then on not adding "node". -- GitHub Notification of comment by jan-ivar Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/158#issuecomment-863513237 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 17 June 2021 19:41:31 UTC