Re: [WebIDL] Allowing specifications to opt in to throwing on sets of enumerated attributes to invalid values

On Thursday, November 15, 2012 at 3:09 PM, Boris Zbarsky wrote:

> > Worst case, you end up with something like:
> >  
> > try{
> > = value;
> > //did it really assign the value?
> > if( === value){
> Why do you need that if check? The whole point of [strict] is that if
> it didn't throw, it assigned the value.

Yeah, I realized that after I sent it… but assume Version 0 works like WebIDL does today. So, a value may or may not be set (as it may fall back to a default), so you need to confirm that it actually worked. If Version 1 switches to [strict], then you need the above check to catch Version 0, no?

Marcos Caceres

Received on Thursday, 15 November 2012 16:03:50 UTC