W3C home > Mailing lists > Public > www-dom@w3.org > April to June 2009

Re: Travis - Jonas - João replies [DOML3Events] ACTION-267 Proposal for event iterator

From: Charles McCathieNevile <chaals@opera.com>
Date: Wed, 29 Apr 2009 01:20:10 +0200
To: "DOM public list" <www-dom@w3.org>
Message-ID: <op.us4drwcowxe0ny@widsith.local>
> Jonas wrote:
> <Travis.Leithead@microsoft.com> wrote:
>> I think this was dropped because it would allow general web apps
>> to inspect (and remove?) event handlers that were registered by
>> code running in extensions or by the browser itself.
>>  In general, this is a great idea for debugging or extensions,
>> but not so great in web app deployment scenarios.
>>  Folks can feel free to correct me if I'm way off base.

> That is the initial problem that we in firefox would have with this.

> The other problem is a lack of use cases. All the ones I have heard so
> far has been to implement various aspects of accessibility technology.
> However this can be done using internal interfaces in the UA. No need
> to expose anything to web pages.

> / Jonas

Also, this would obviously conflict with client side user scripts which I  
would not like to see :), because then a webpage would clear all the  
local  script listeners, while it should really be the user to say how the  
site should behave ultimatelly.

On Wed, 29 Apr 2009 01:05:34 +0200, Charles McCathieNevile
<chaals@opera.com> wrote:

> (forwarded from public-webapps - I will add the current replies from  
> there to this thread)
>
> ------- Forwarded message -------
> From: "Mike Wilson" <mikewse@hotmail.com>
> To: public-webapps@w3.org
> Cc:
> Subject: RE: [DOML3Events] ACTION-267 Proposal for event iterator
> Date: Sat, 25 Apr 2009 11:35:54 +0200
>
> Following up on last year's discussion on adding support for
> querying DOM elements about already registered event handlers:
>
> Travis Leithead wrote on Apr 09, 2008; 08:07pm
>> In considering a design for the event iterator (allow devs
>> to enumerate what events have been _added_ via
>> addEventListener to a given object), I looked at two general
>> approaches:
>>
>> 1) Defining a new collection on every object that supports
>> the EventTarget interface
>> 2) Defining a 'getNextEvent' function for every object that
>> supports the EventTarget interface
>> 3) Defining a function that returns a static/dynamic list of
>> event handlers for a given object that supports the
>> EventTarget interface
> <rest of conversation snipped>
>
> Action page:
> http://www.w3.org/2006/webapi/track/actions/267
>
> Mail thread view on nabble:
> http://www.nabble.com/-DOML3Events--ACTION-267-Proposal-for-event-iterator-t
> d16593177.html#a16691378
>
> Was any consensus ever reached and what's the status of this
> suggestion now?
>
> Personally I think this feature is a very natural part of the
> DOM API and believe there needs to be very good reasons not to
> include it.
>
> Best regards
> Mike Wilson
>
>
>



-- 
Charles McCathieNevile  Opera Software, Standards Group
      je parle français -- hablo español -- jeg lærer norsk
http://my.opera.com/chaals       Try Opera: http://www.opera.com
Received on Tuesday, 28 April 2009 23:20:56 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Friday, 22 June 2012 06:14:00 GMT