This event is used to signal if, during operation, the settings of the track changed in such a way that it is not possible to satisfy the constraints for this track any longer. If so, the offending track is muted and the event is raised so that the application can address the problem appropriately. This is useful for getting more consistent behavior across browsers and allow for better control for the application.


Specification link

Specification being incubated in a Community Group

Status in Chromium


No longer pursuing (tracking bug)

Consensus & Standardization

After a feature ships in Chrome, the values listed here are not guaranteed to be up to date.



The W3C WebRTC working group has decided to remove this feature from the specifications due to lack of use cases that would justify it. Working group decision: PR that removed the feature:

Search tags

overconstrainederrorevent, getusermedia,

Last updated on 2021-07-20