- From: Christopher M. Balz <christophermbalz@stanfordalumni.org>
- Date: Sun, 20 Sep 2009 00:33:34 -0700 (PDT)
- To: Cameron McCormack <cam@mcc.id.au>
- Cc: www-dom@w3.org
Thank you for the reply! I agree - I don't know IDL but it looks like the spec enables this via the mixin prototype object in the 'Node' object diagram. Perhaps this could use some additional explanation (http://dev.w3.org/2006/webapi/WebIDL/#PrototypeRoot and scroll down) - "Editorial note Maybe the functions on mixin prototype objects should just call the relevant function on the original interface’s prototype object." Since interfaces don't have implementations of methods, what would the Editorial note's suggestion do? Thank you, - cb ----- Original Message ---- From: Cameron McCormack <cam@mcc.id.au> To: Christopher M. Balz <christophermbalz@stanfordalumni.org> Cc: www-dom@w3.org Sent: Friday, September 18, 2009 12:31:42 AM Subject: Re: How to get event listener method inheritance clarified Hi Christopher. Christopher M. Balz: > Imho, the DOM spec should clearly state where the 'addEventListener' > and 'removeEventListener' methods should be located in the 'Element' > inheritance hierarchy. > … > Could this be included in a spec update? Web IDL specifies this, but not currently in a way that describes what implementations do at the moment: http://dev.w3.org/2006/webapi/WebIDL/#interface-prototype-object We’ll see how well the browser vendors take to it once we go to Last Call. -- Cameron McCormack ≝ http://mcc.id.au/
Received on Sunday, 20 September 2009 07:34:16 UTC