W3C home > Mailing lists > Public > www-dom@w3.org > July to September 2009

Re: Can Dispatch canDispatch()?

From: Maciej Stachowiak <mjs@apple.com>
Date: Wed, 26 Aug 2009 13:25:51 -0700
Cc: DOM mailing list <www-dom@w3.org>
Message-id: <9BA90325-3990-4142-A3C1-B304FB419980@apple.com>
To: Doug Schepers <schepers@w3.org>

On Aug 26, 2009, at 1:16 PM, Doug Schepers wrote:

> Hi, Folks-
> A little more digging (and pestering PLH) shows that canDispatch()  
> was added because MS didn't want to implement some aspects of  
> Mutation events [1], so the decision was made to allow authors to  
> discover if a particular event is supported by the implementation  
> [2] (look for "willImplementationDispatch").
> It does seem that, once introduced, it was repurposed for the more  
> general case, such as detecting if a Custom Event would be  
> dispatched [3].  I am not sure these are quite the same use case,  
> and I think this introduces even more ambiguity into canDispatch().
> To me, this seems like evidence that we should drop canDispatch()  
> for now, and approach the problem from a different angle, with  
> proper use cases and requirements.
> If I don't hear objections in the next two weeks, I will drop this  
> method from the next draft.  I have already marked it as At Risk.

Sounds like a good decision to me. I agree with this reasoning.

Received on Wednesday, 26 August 2009 20:26:34 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 20 October 2015 10:46:15 UTC