- From: Dominique Hazael-Massieux <dom@w3.org>
- Date: Wed, 16 Dec 2015 09:55:57 +0100
- To: Adam Bergkvist <adam.bergkvist@ericsson.com>, "public-media-capture@w3.org" <public-media-capture@w3.org>
On 16/12/2015 09:50, Adam Bergkvist wrote: > I'm leaning towards treating known but unsupported constraints/features > the same as "future constraints". That would mean that if a constraint > name is present in MediaTrackSupportedConstraints, it's not only that > the browser won't ignore that constraint if used, but it can also do > something useful with it and not only report that it's always turned off. > > What do you think? It was designed that way, and I think it has to be that way; while in the case of echo cancellation, it could be argued that always answering false is OK, what would be the equivalent for frameRate or width? Dom
Received on Wednesday, 16 December 2015 08:56:04 UTC