- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Thu, 19 May 2022 15:08:34 +0000
- To: public-webrtc-logs@w3.org
I agree with @jan-ivar here. > * I think we should allow it to fail if the implementation does not yet support a specific Element type, for a start. Ideally all implementations will support all Element types. But we don't live in an ideal world. It seems out of scope of this particular issue, WebIDL should solve this without the spec saying anything. > * It sounds quite reasonable to also allow failure for reasons of resource-limitations in the browser. Why? This is a pattern we do not see in any spec. As already said, this is a potential privacy issue as implemented in Chrome and I do not see why we should specify behaviours with such hazards. > * I think `cropTo()` should also be allowed to fail for resource-limitation, while we're at it. That sounds ok to me. cropTo is an expensive method, it already has an error code path, reusing it is not harmful. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/48#issuecomment-1131848396 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 19 May 2022 15:08:35 UTC