W3C home > Mailing lists > Public > public-media-capture@w3.org > February 2015

Re: List attention: Meaning of bare values in "advanced" constraints?

From: Stefan Håkansson LK <stefan.lk.hakansson@ericsson.com>
Date: Tue, 10 Feb 2015 12:49:23 +0000
To: Harald Alvestrand <harald@alvestrand.no>, "public-media-capture@w3.org" <public-media-capture@w3.org>
Message-ID: <1447FA0C20ED5147A1AA0EF02890A64B1D189693@ESESSMB209.ericsson.se>
On 10/02/15 12:52, Harald Alvestrand wrote:
> Jan-Ivar raised the following issue in the tracker:
>
> https://github.com/w3c/mediacapture-main/issues/128
>
> The construct under discussion is this:
>
>   var  constraints=
>    {
>      width:  {min:  640,  ideal:  1280},
>      height:  {min:  480,  ideal:  720},
>      advanced:  [{width:  1920,  height:  1280},
>                 {aspectRatio:  1.3333333333}]
>    };
>
>
> The question is: are the bare values in "advanced" intended as "exact"
> or "ideal"?
>
> If "ideal", the algorithm needs to specify how to deal with multiple
> "ideal" values for the same list of constraints - which one applies?
>
> If "exact" (which was clearly intended by the example originally), the
> algorithm needs to specify that bare values are exact in one context and
> ideal in the other. Dom has a pull request doing this here, with some
> discussion:
>
> https://github.com/w3c/mediacapture-main/pull/132
>
> Before we fixate on exact text, it seems good to verify what the WG wants.
> Are we happy to see bare values mean "ideal" in top level and "exact" in
> "advanced"?

(contributor hat) yes.

>
> Harald
>
Received on Tuesday, 10 February 2015 12:49:50 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 10 February 2015 12:49:50 UTC