W3C home > Mailing lists > Public > public-webapi@w3.org > March 2006

Re: ACTION-70: Define the scope chain of onFoo events reference issue-1

From: Jonas Sicking <jonas@sicking.cc>
Date: Wed, 15 Mar 2006 05:22:47 -0800
Message-ID: <44181527.8010209@sicking.cc>
To: Bjoern Hoehrmann <derhoermi@gmx.net>, Web APIs WG <public-webapi@w3.org>

Bjoern Hoehrmann wrote:
> * Jonas Sicking wrote:
>> Do we really only want to do this for HTML attributes? It's not a 
>> particularly beautiful thing to do, but on the other hand it's always 
>> nice when things behave everywhere.
> 
> Well, this behavior is pretty much limited to HTML onfoo="" attributes,
> you don't have it for SVG onfoo="" attributes in most implementations,
> or addEventListener listeners, or <script> listeners, ... and since you
> would ultimiately have to change handleEvent's signature, I don't think
> that is a good idea.

My suggestion was only to do this for onfoo attributes. Not for 
addEventListener calls or <script> listeners. So there is no need to 
change the signature of handleEvent.

> Note that this isn't as simple as if the return
> value is false: preventDefault; what you do depends on the event type.

Are you referring to the fact that for the mouseover event (or was it 
some other mouse* event?) the return value should be true to call 
preventDefault?

/ Jonas
Received on Wednesday, 15 March 2006 13:22:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:53 GMT