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

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 using your GitHub account

Received on Friday, 8 March 2019 13:47:36 UTC