- From: Elad Alon via GitHub <sysbot+gh@w3.org>
- Date: Mon, 31 Jan 2022 20:43:22 +0000
- To: public-webrtc-logs@w3.org
A central repository is an implementation detail. The spec should not accidentally disallow reasonable implementations (hence the Promise). The spec is not concerned with such details beyond that point. It's undesirable to put in the token more information than strictly necessary. By ensuring that CropTargets do not encode information about their source, we can provide better guarantees about the safety of the entire mechanism. (Please note - information not exposed to JS, but potentially available to a malicious application which has taken over the process, is also undesirable. Information not encoded in the render process cannot leaked to a malicious application.) > Also this issue was mostly about MediaDevices or Element and it is heavily going in Promise or not. > Maybe we should have a specific issue for discussing whether promising or not. If my current comment has not been sufficient to convince you, you're welcome to continue the discussion in a spin-off issue. --- I wonder if anyone else (@jan-ivar, @aboba, @alvestrand) has an opinion to voice about exposing as `MediaDevices.produceCropTarget()` vs. exposing as `Element.cropTarget()`. -- GitHub Notification of comment by eladalon1983 Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/11#issuecomment-1026191446 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 31 January 2022 20:43:25 UTC