also note that this would mean that a web site could try to knock out
other web based mashups that it didn't like.
i'm sure that browser vendors can provide an api for their debugging
clients, but this feature shouldn't be exposed to web content.
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
On Tue, Apr 28, 2009 at 12:50 PM, Travis Leithead
travis.leith...@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
On Tue, 28 Apr 2009 21:57:10 +0200, Jonas Sicking jo...@sicking.cc wrote:
On Tue, Apr 28, 2009 at 12:50 PM, Travis Leithead
travis.leith...@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
/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
