W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > May 2022

Re: [mediacapture-region] Should generation of CropTarget from elements be able to fail? (#48)

From: Elad Alon via GitHub <sysbot+gh@w3.org>
Date: Mon, 23 May 2022 13:44:07 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1134698610-1653313444-sysbot+gh@w3.org>
> Throwing an exception/rejecting a promise might be fine, using WebIDL or synchronous checks.

So let's go for it and have one less outstanding issue. If I send a PR that says that a synchronous error should be raised if the element is not of a type supported by the implementation, will you approve it? We can discuss other failures separately.

> At the time, I remember you saying this was out of scope since we were going with Element.

I only have a vague memory of this discussion. The current implementation in Chrome, as of the time of this writing, is [here](https://source.chromium.org/chromium/chromium/src/+/main:third_party/blink/renderer/modules/mediastream/media_devices.idl;l=45-53;drc=d7340db3593236e1a8351a736c372b89df002814) - always has been `HTMLDivElement and HTMLIFrameElement`. Long-term, I expect everyone to support any Element, and feature-discovery to be unimportant. But for the short-term, with only some Elements being supported by implementations, I think the spec should make an affordance.

GitHub Notification of comment by eladalon1983
Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/48#issuecomment-1134698610 using your GitHub account

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 23 May 2022 13:44:08 UTC

This archive was generated by hypermail 2.4.0 : Saturday, 6 May 2023 21:19:57 UTC