Re: How to handle known but unsupported constraints

On 2015-12-16 09:56, Dominique Hazael-Massieux wrote:
> 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?

If only one frameRate and resolution (width) is supported, it's 
interesting to know the exact numbers from the capabilities. The 
question is if the same applies to a toggle on/off feature like echo 
cancellation.

/Adam

Received on Wednesday, 16 December 2015 10:30:31 UTC