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

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