|Remove MediaConstraintsInterface from webrtc|
|Project Member Reported by email@example.com, Mar 2 2016||Back to list|
Once Chrome no longer uses MediaConstraintsInterface, try to remove it from webrtc/api. This should flush out other existing users. The existing API where we have functionality that can't be done without constraints is CreateVideoSource - but that functionality isn't used by Chrome. We need to identify users before we can design an alternative. Eng owner: firstname.lastname@example.org
Mar 2 2016,
Sep 20 2016,
We still use CreateVideoSource with constraints for the iOS capture implementation, but we probably want to move away from that.
Dec 11 2016,
[Bulk edit] This issue was created more than a year ago and hasn't been modified the last six months -> archiving. If this is still a valid issue that should be open, please reopen again.
|► Sign in to add a comment|