Re: Can Dispatch canDispatch()?

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.

Regards,
Maciej