- From: Craig Northway <craign@cisra.canon.com.au>
- Date: Fri, 20 May 2005 09:49:39 +0900
- To: Masahiko Kono <kono.masahiko@canon.co.jp>
- Cc: www-svg@w3.org, Jon Ferraiolo <jon.ferraiolo@adobe.com>
Hi, These particular examples now specify the event names qualified in the XML Events namespace, i.e. ev:click where ev is the XML Events namespace. Regards, Craig Northway Craig Northway wrote: > > Jon, > > Surely the examples in the SVG Tiny 1.2 specification should indicate > the namespaced event name, ev:click. > > Regards, > Craig > > Jon Ferraiolo wrote: > >> >> "click" and "ev:click" are equivalenced, so you can say either. >> >> Most older W3C spec, including SVG 1.0/1.1, used DOM2 Events which >> did not support namespacing. With DOM3 Events, namespaced events were >> introduced and all of the standard events defined in the DOM3 Events >> spec were defined to be in the XML Events namespace. Thus, "click" >> was defined to be in ev:click. The only way to make it so that old >> content which just said "click" would still work in a user agent >> which moves up to DOM3 Events is to say that "click" and "ev:click" >> are equivalenced. >> >> Jon >> >> At 02:14 AM 5/19/2005, KONO Masahiko wrote: >> >>> Dear SVG WG, >>> >>> 15.3 XML Events >>> >>> SVG Tiny 1.2 uses namespaced events. How can I deal namespace of >>> events? >>> In examples(handler.svg, javahandler.svg), 'click' event is registered. >>> Should event attribute value be qualified(ev:click)? >>> >>> Best regards, >>> >>> -- >>> KONO Masahiko >>> CANON INC. >>> E-mail : kono.masahiko@canon.co.jp >> >> >> >> >> > >
Received on Friday, 20 May 2005 00:49:49 UTC