W3C home > Mailing lists > Public > public-webapi@w3.org > April 2008

Re: [DOML3Events] ACTION-267 Proposal for event iterator

From: Maciej Stachowiak <mjs@apple.com>
Date: Wed, 9 Apr 2008 14:50:59 -0700
Cc: Anne van Kesteren <annevk@opera.com>, Doug Schepers <schepers@w3.org>, Web API public <public-webapi@w3.org>
Message-Id: <B52E59D5-0C2B-4DEC-9027-94C70F9F129F@apple.com>
To: Travis Leithead <travil@windows.microsoft.com>


On Apr 9, 2008, at 2:16 PM, Travis Leithead wrote:

>
> I've been specifically requested to add such support into IE by  
> various customers. Most of their use-cases involve script that is  
> trying to 'clean-up' event handlers for which they did not set, and  
> do not have a pre-existing handle to the function callback.

Could you be more specific about the use cases? That sounds pretty  
vague, and from your example, it's also not clear that enumeration is  
even the most useful API to address these use cases. It sounds like an  
API to clear all event listeners on a node would be more appropriate.

I also wonder why anyone would want to remove event handlers that they  
did not install themselves, we have not received requests like this  
for Safari or WebKit. I wonder if this might be due to the fact that  
leaving event listeners attached after leaving the page can cause  
memory leaks in IE. Other browsers don't have this problem, so I think  
the right solution, if this is the motivation, would be to fix the  
memory leaks.

Also I am not sure why IE customers would be requesting extensions to  
DOM Events, since IE doesn't yet support DOM Events at all. (Though to  
be fair, perhaps you are translating requests for extensions to IE's  
event model into requests for extensions to DOM events.)

Regards,
Maciej
Received on Wednesday, 9 April 2008 21:51:43 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 9 April 2008 21:51:45 GMT