We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Incorrect support data (example: BrowserX says "86" but support was added in "40")
Chrome does not support applyConstraints: https://issues.chromium.org/390804131
Chromium (Chrome, Edge 79+, Opera, Samsung Internet)
applyConstraints is not supported
Yes, I tried to use the api, and the getSettings response did not update. Also validated that echoCancellation had not changed.
https://issues.chromium.org/390804131
No response
https://developer.mozilla.org/en-US/docs/Web/API/MediaStreamTrack/applyConstraints
api.MediaStreamTrack.applyConstraints
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What type of issue is this?
Incorrect support data (example: BrowserX says "86" but support was added in "40")
What information was incorrect, unhelpful, or incomplete?
Chrome does not support applyConstraints: https://issues.chromium.org/390804131
What browsers does this problem apply to, if applicable?
Chromium (Chrome, Edge 79+, Opera, Samsung Internet)
What did you expect to see?
applyConstraints is not supported
Did you test this? If so, how?
Yes, I tried to use the api, and the getSettings response did not update. Also validated that echoCancellation had not changed.
Can you link to any release notes, bugs, pull requests, or MDN pages related to this?
https://issues.chromium.org/390804131
Do you have anything more you want to share?
No response
MDN URL
https://developer.mozilla.org/en-US/docs/Web/API/MediaStreamTrack/applyConstraints
MDN metadata
MDN page report details
api.MediaStreamTrack.applyConstraints
The text was updated successfully, but these errors were encountered: