W3C home > Mailing lists > Public > public-media-capture@w3.org > August 2016

Re: [mediacapture-main] Should we use [EnforceRange] on min/max in constraints?

From: Martin Thomson <martin.thomson@gmail.com>
Date: Mon, 22 Aug 2016 16:20:48 +1000
Message-ID: <CABkgnnXhJvOowYZ6CPpKe+dENY7Pa2QbvHNj6iUwU8AoUBdeOw@mail.gmail.com>
To: Harald Alvestrand via GitHub <sysbot+gh@w3.org>
Cc: "public-media-capture@w3.org" <public-media-capture@w3.org>
On 19 August 2016 at 22:25, Harald Alvestrand via GitHub
<sysbot+gh@w3.org> wrote:
> Would the behavior specified at https://www.w3.org/TR/WebIDL/#es-long
> for [EnforceRange] (which is "throw a TypeError") be a less surprising
>  behavior for users?

This is probably best.  As you say, this is a crazy test, but getting
0 is surprising.  It's worse when you consider what { max: Infinity }
gets you.
Received on Monday, 22 August 2016 06:21:17 UTC

This archive was generated by hypermail 2.3.1 : Monday, 22 August 2016 06:21:17 UTC