> ```js > [ > SecureContext, > Exposed=(Window,Worker), > Serializable > ] interface CropTarget { > static Promise<CropTarget> fromElement(Element element); > }; > ``` CropTarget should probably not be SecureContext, nothing prevents CropTarget to be serialized from a secure context to a non secure context AFAIK. The debate is more to decide whether we want fromElement to be gated by SecureContext. The use case is whether a secure capturer would potentially want to crop a non secure capturee if/when cross-page cropping is supported. I am curious what the rationale is for marking it as SecureContext (other than the mantra of new API = SecureContext). -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/11#issuecomment-1132590803 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-configReceived on Friday, 20 May 2022 07:49:27 UTC
This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:57 UTC