W3C home > Mailing lists > Public > public-script-coord@w3.org > July to September 2013

Re: Maybe we should think about Interface.isInterface functions again

From: Boris Zbarsky <bzbarsky@MIT.EDU>
Date: Sat, 20 Jul 2013 16:44:43 -0400
Message-ID: <51EAF6BB.3020200@mit.edu>
To: Anne van Kesteren <annevk@annevk.nl>
CC: Domenic Denicola <domenic@domenicdenicola.com>, Travis Leithead <travis.leithead@microsoft.com>, "public-script-coord@w3.org" <public-script-coord@w3.org>
On 7/20/13 12:08 PM, Anne van Kesteren wrote:
> So why does the attribute getter in
> http://dev.w3.org/2006/webapi/WebIDL/#dfn-attribute-getter throw?

The main reasons are that the UAs that had such getters threw in this 
situation and the boolean attribute issue...  If we don't care about 
this, we could just give all getters the LenientThis behavior, I suppose.

> Could you give an example of how that would go wrong?

Sure:

   if (stylesheet.disabled) {
   }

if your object happens to not be a stylesheet but rather the StyleSheet 
prototype, you'll get back undefined with the LenientThis behavior and 
then it'll test as enabled... which is a bit odd.  But maybe this really 
is an edge case.

I would be willing to try making all getters LenientThis and seeing what 
happens.

For setters, I think throwing on incorrect this still makes sense, 
though, right?

-Boris
Received on Saturday, 20 July 2013 20:45:13 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:37:50 UTC