Contact emails
os...@chromium.org, gru...@chromium.org
Explainer
Summary
Motivation
For experimental usage, this feature allows browser vendors (such as Chrome) to evaluate the performance of new, experimental echo cancelers in the wild. Letting the web application control which echo canceler is being used allows them a way to easily switch away from a new implementation, were it to prove problematic.
Outside of pure experimentation, the echoCancellationType constraint will allow applications to black list system-level echo cancelers, for example on specific models or when used with specific input devices. Building such a blacklist within each browser would be a terribly slow process, not least due to long release cycles and duplicated effort. An application-level blacklist can be built up communally and be released publicly, e.g. on github.
Risks
Interoperability and Compatibility
Applications can check MediaTrackSupportedConstraints and/or MediaTrackCapabilities before using this new constraint. If it's unavailable, or has only a limited set of options (e.g. only 'browser' or 'system'), the application can adapt.
Ergonomics
Performance should not be affected.
Activation
Using the new constraint in an experiment, to access the new system-level echo cancelers, is very straightforward.
To get the full benefits of this new functionality, a blacklist/whitelist will have to be created. As mentioned, this can be a communal effort.
Will this feature be supported on all six Blink platforms (Windows, Mac, Linux, Chrome OS, Android, and Android WebView)?
Link to entry on the feature dashboard
I'm not sure if this requires a feature just yet. I'll create one if needed.
Requesting approval to ship?
No