On 10/10/18 4:29 PM, Mike Taylor wrote:
Hi Jan-Ivar,
On 10/10/18 9:48 AM, Jan-Ivar Bruaroey wrote:
The most likely net fallout of, if any, would be sites that UA-sniff
AND rely on the legacy Firefox names ONLY to turn OFF audio
processing. These are likely to be specialty sites dealing with things
like music rather than your typical WebRTC communication site. More
likely, old sites would double up the moz and non-moz constraints here
in order to work with both Firefox and Chrome, and in those cases,
there is no impact.
If they didn't include an unprefixed constraint, would it throw?
No, they'd get processed audio where they expected unprocessed audio.
.: Jan-Ivar :.
_______________________________________________
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
