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: youennf via GitHub <sysbot+gh@w3.org>
Date: Mon, 23 May 2022 07:08:38 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1134267749-1653289716-sysbot+gh@w3.org>
> * If we standardize that `Element` should be received, and one browser accepts `(IFrame or Div)`

Do we have such case? I would hope not.
In Chrome's case, my understanding is that the WebIDL might accept HTMLElement and not Element, this is fine and is handled by WebIDL just fine.

> * Do we now specify in the IDL that we support `(ElementType1 or ElementType2 or ... ElementType2950)`?

We could if we think this makes sense. Some API support BufferSource, some only ArrayBuffer.
If we have to go down there, we should probably rethink our API shape though.

> [This](https://www.w3.org/TR/mediacapture-streams/#methods-6) is not identical, but it's similar:

How is it similar?
There are hardware limitations which do not allow to support more than a maximum number of pixels, a UA must have to deal with these limitations.
In our case, failing a CropTarget is due to a UA optimisation to reduce latency. The UA could have decided to go with another approach.

GitHub Notification of comment by youennf
Please view or discuss this issue at https://github.com/w3c/mediacapture-region/issues/48#issuecomment-1134267749 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 07:08:40 UTC

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