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

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

From: Jonas Sicking <jonas@sicking.cc>
Date: Mon, 14 Apr 2008 14:58:48 -0700
Message-ID: <4803D398.6030700@sicking.cc>
To: "Hallvord R. M. Steen" <hallvord@opera.com>
CC: Maciej Stachowiak <mjs@apple.com>, Travis Leithead <travil@windows.microsoft.com>, Anne van Kesteren <annevk@opera.com>, Doug Schepers <schepers@w3.org>, Web API public <public-webapi@w3.org>

Hallvord R. M. Steen wrote:
> 
> On Wed, 09 Apr 2008 23:50:59 +0200, Maciej Stachowiak <mjs@apple.com> 
> 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?
> 
> One use case that hasn't come up but may be better supported by other 
> means: debugging.
> As far as I can see, there is no view in, say, Firebug that shows me an 
> overview of event listeners added with addEventListener(). In many cases 
> this would be very useful.
> 
> (By "better supported by other means" I meant that an alternative would 
> be to enable something like the proposed functionality in "debug mode" 
> or "debug builds" only. It seems more useful to me personally to simply 
> have it available though.)

Like Boris points out, there is no need to expose debugging APIs to web 
pages. Browsers can expose those thorough internal APIs to their tools.

There is no API to enabling stepping through javascript or breaking on 
all exceptions either.

/ Jonas
Received on Monday, 14 April 2008 22:01:25 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 14 April 2008 22:01:26 GMT