W3C home > Mailing lists > Public > public-webrtc-logs@w3.org > March 2019

Re: [mediacapture-main] Why do we have overconstrained event? (#573)

From: Jan-Ivar Bruaroey via GitHub <sysbot+gh@w3.org>
Date: Fri, 08 Mar 2019 13:47:35 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-470933851-1552052854-sysbot+gh@w3.org>
I'd vote for B. Firefox never implemented it, and no-one has asked us for it.

> I think it's up to the application whether or not to mute the track, otherwise this is a foot-gun.

Agree. I think it's a web compat issue at this point: if implemented literally, any application already using `{frameRate: {min: 60}}` today and ***not*** listening to the `overconstrained` event, would suddenly have its track muted in low light.

I claim no-one wants that. If the expectation is the application *immediately* corrects the overconstrained situation, then nothing seems lost by leaving the track unmuted. So 👍 for A.1.

GitHub Notification of comment by jan-ivar
Please view or discuss this issue at https://github.com/w3c/mediacapture-main/issues/573#issuecomment-470933851 using your GitHub account
Received on Friday, 8 March 2019 13:47:36 UTC

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