Why even consider eventListener when XML already has adequate methods to handle the event attribute for an SVG element. Please!, Show me something that the DOM, excluding the redundancy of eventListener, cannot handle. Francis
--- In [email protected], Robin Berjon <[EMAIL PROTECTED]> wrote: > Francis Hemsher wrote: > > I've fiddled with addEventListener, but no matter how I played it, I > > could always use XML and the DOM methods to handle events for an svg > > element in a much more elegant manner. > > We all have ways in which we prefer to do some things, but that doesn't > mean that the other ways that other people may find more useful need to > be removed. If you don't like it, don't use it! > > I have found addEventListener extremely useful, especially when > attaching events to elements created dynamically or when I need to bind > and unbind events dynamically. It's quite elegant, and doing the same > with other methods would be either impossible or quite hackish. > > You mention using DOM methods to handle events, but I'm not sure what > you mean as addEventListener *is* the DOM way of setting event listeners. > > -- > Robin Berjon > Research Scientist > Expway, http://expway.com/ ----- To unsubscribe send a message to: [EMAIL PROTECTED] -or- visit http://groups.yahoo.com/group/svg-developers and click "edit my membership" ---- Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/svg-developers/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
