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

Re: [mediacapture-region] What should the spec say about elements like HTMLAudioElement? (#51)

From: Elad Alon via GitHub <sysbot+gh@w3.org>
Date: Fri, 27 May 2022 17:56:41 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-1139897481-1653674199-sysbot+gh@w3.org>
> but can we agree this is irrelevant here?

Bugs are irrelevant and transitory. But abiding incompatibilities such as elements looking completely different between implementations, up to and including capturing background pixels in some implementations but not in others, is very relevant.

> It doesn't restrict or convey judgement about whether what you're trying to accomplish is "sensible" or not

The difference is that with requestFullscreen(), at worst you get slightly silly behavior for the local user, whereas with cropping, you could be exposing a different set of pixels to remote participants, possibly unbeknownst to the local user.

> It's more work on browser vendors to make it KISS for web developers

It's good and proper for browsers to pay for developers' lunch, but only if developers are going to eat it. Here, I think we'd be wasting time and effort on unrequested, undesired functionality, that no prudent developer would use. So far, developers seem to be happy with cropping to DIVs. We have expanded the scope all the way to Element rather speculatively.

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

Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 27 May 2022 17:56:42 UTC

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