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

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

From: henbos via GitHub <sysbot+gh@w3.org>
Date: Fri, 08 Mar 2019 09:13:18 +0000
To: public-webrtc-logs@w3.org
Message-ID: <issue_comment.created-470858902-1552036396-sysbot+gh@w3.org>
Proposal A

In order of importance, but 2. and 3. are up for discussion.
1. Don't mute a track that gets overconstrained, it makes it a foot-gun and it contradicts the definition of being muted means: "live samples are not made available to the MediaStreamTrack".
2. Add a boolean overconstrained attribute to indicate whether or not it is currently overconstrained.
3. Add an onunoverconstrained event.

Proposal B

1. Remove overconstrained event. Let the application implement "is overconstrained" logic if it cares about this.

@armax00 @jan-ivar @guidou

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

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