- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Tue, 29 Mar 2022 13:29:36 +0000
- To: public-webrtc-logs@w3.org
> Another problem I have with a slot that holds a "weak reference" to an Element, is that it becomes needlessly scary when considering later extensions of this API to cropping a track derived from capturing another tab. @eladalon1983, with regards to https://github.com/w3c/mediacapture-region/pull/24#issuecomment-1080970113, if you invoke security concerns, please provide as precise security assessments. I honestly do not understand your message, or how it weakens weak :0) references. FWIW, the web is full of well dealt with relationships between objects from different origins, living in potentially different processes which have security implications. Security will be best ensured and assessed with precisely defined relationships, semantics and algorithms This is the intent of this work, there is no intent in changing the behavior or outlawing a particular implementation. > If you're sure about that, then we can throw on `forStorage` as far as I'm concerned. An important part of the standardisation is to cross check and make sure we are all on the same page after this work. In other words, do not trust me and please cross-check ;o) -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-region/pull/24#issuecomment-1081874301 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Tuesday, 29 March 2022 13:29:38 UTC