Re: [Bug 25766] New: Problem with constraints failure when there is no constraint.

On 5/19/14 12:27 PM, Jim Barnett wrote:
> Maybe we're talking past each other.  WebIDL does not guarantee 
> failure, hence the need for the "require" element.  The question is 
> what happens when the UA doesn't find a 'require' element in the 
> dictionary that gets passed in.  Is your idea that UAs know what they 
> don't support, so that if they find an unsupported property on 
> 'require', they can fail the call,  whereas if they find a supported 
> property on 'require' but not in the dictionary, they should let the 
> call succeed?

Yes.

>   For an edge case, what if the author puts an unsupported property in 
> 'require' but doesn't include it in the dictionary?

I think it should fail.

Disclaimer: I'm speaking solely as an implementer. It's what seemed most 
natural: I scanned the "require" array for alien things to fail on, 
without looking at the rest of the dictionary. Later, when I evaluate 
top-level dictionary members, I look in "require" to know what type of 
constraint it is. The two things are nicely untangled this way. - I'll 
happily yield to any real use-case needs.

.: Jan-Ivar :.

Received on Monday, 19 May 2014 17:28:54 UTC