- From: youennf via GitHub <sysbot+gh@w3.org>
- Date: Fri, 24 Mar 2023 09:06:15 +0000
- To: public-webrtc-logs@w3.org
> It exists specifically to solve the narrow problem where non-failure of an `exact` [_"constraint being ignored due to lack of support in a user agent is not tolerated by the application"_](https://w3c.github.io/mediacapture-main/#example-10). Since `exact` constraints are [largely deprecated](https://w3c.github.io/mediacapture-main/#dfn-allowed-required-constraints-for-device-selection) in new specs, there should be no need to extend this pattern. Now that MediaStreamTrack can be created outside of getUserMedia in all browsers (say via peer connection), mediaDevices.getSupportedConstraints() is no longer strictly needed to solve this narrow problem. Also, this raises the question whether we should continue to extend MediaTrackSupportedConstraints for new constraints. We are doing this in mediacapture-extensions currently. -- GitHub Notification of comment by youennf Please view or discuss this issue at https://github.com/w3c/mediacapture-screen-share/issues/260#issuecomment-1482471853 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Friday, 24 March 2023 09:06:16 UTC