Re: [Bug 22593] Capabilities are buggy

On 04/03/2014 11:31 AM, Dominique Hazael-Massieux wrote:
> On jeu., 2014-04-03 at 11:21 +0200, Harald Alvestrand wrote:
>> No, I think you're misreading the semantics here.
>> This will match all devices that have facingMode either user or environment.
> Hmm… I'm talking about capabilities here, not constraints.
>
>
>> Each camera can only have a single value for facingMode, but it makes
>> perfect sense to say that multiple values for facingMode are acceptable.
> Right, but capabilities are about what values a camera can expose.

Hm. This is something that has changed with the introduction of the
Constrainable interface.

It used to be that this text was what we intended to say:

" The Capabilities dictionary specifies the subset of the constrainable
properties and values from the registry that the UA supports". (section
11.3)

and that it was a static method.
Now it is a method on the track, and it is said that:

"The getCapabilities() method returns the dictionary of the capabilities
that the object supports." (section 11.1.2).

Obviously, if the latter is the only thing available, the example is flawed.
If the former is going to be true, there will have to be a static
method, or a method on NavigatorUserMedia, that exposes the
getCapabilities() accessor there.

Which should it be?




>
> Dom
>


-- 
Surveillance is pervasive. Go Dark.