Re: Possible Constraint Syntax Compromise

The consensus seems to be that it's not possible to have the browser know
about an unknown/unexpected key in the constraints object and still work
properly with WebIDL.  Thus, if the constraint is unknown/unexpected, then
the browser can't know about it and that is a problem unless we 1.  throw
out WebIDL or 2.  put in a hack like the "required: ["a", "b", "c"]" in the
current draft, or 3. Say that's OK and let the JS check first.

Out of those three, all the people I talked to preferred #3, which is why I
have proposed it.  If there is something we are all missing about WebIDL
that gives an easier exit from this conundrum, that would be welcome news.


On Tue, May 20, 2014 at 5:49 PM, Timothy B. Terriberry <
tterriberry@mozilla.com> wrote:

> Peter Thatcher wrote:
>
>> handling if it isn't.  It can't expect a browser to blow up if it
>> requires an unsupported constraint.
>>
>
> Wait, why not?
>
>