- From: Bjoern Hoehrmann <derhoermi@gmx.net>
- Date: Wed, 15 Mar 2006 14:55:02 +0100
- To: Jonas Sicking <jonas@sicking.cc>
- Cc: Web APIs WG <public-webapi@w3.org>
* 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. I think the return value should be ignored everywhere (to the extend possible). Current SVG implementations typically don't support this, it's not easy to understand given that the effect depends on the type of event, and the more it works, the more people expect it to work, so they'd likely be surprised if this works for svg onclick="" but not for <svg:handler>, for example. >> 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? Well, something like that. http://esw.w3.org/topic/List_of_events has many events where I don't know what the effect would be... -- Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de 68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/
Received on Wednesday, 15 March 2006 13:55:12 UTC