W3C home > Mailing lists > Public > public-media-capture@w3.org > November 2014

Re: Capabilities vs SupportedConstraints

From: Martin Thomson <martin.thomson@gmail.com>
Date: Wed, 5 Nov 2014 15:22:01 -0800
Message-ID: <CABkgnnWhiksgF_XRzn_0=kqOH4SWYVz8NtQzDMwPBujCRicp0Q@mail.gmail.com>
To: Rob Manson <robman@mob-labs.com>
Cc: "public-media-capture@w3.org" <public-media-capture@w3.org>
On 4 November 2014 15:40, Rob Manson <robman@mob-labs.com> wrote:
> Supported Constraints are the sub-set of Constraints that both the device
> AND the UA are able to understand and attempt to apply (this is not just the
> constraint-parsing table but also what the device drivers support).

I don't see how this can be implemented without restructuring the API
in a way that makes gUM less usable.

How about having "recognized constraints" instead, which is the set of
constraints that the UA knows about and will either a) reject if it
can't apply them for any reason, or b) apply them.
Received on Wednesday, 5 November 2014 23:22:29 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:26:31 UTC