|
From: C. M. Sperberg-M. <cm...@bl...> - 2013-07-24 22:45:29
|
If I understand correctly what my code is telling me, the second argument to an event listener is an event object named 'event' in the namespace http://www.w3.org/1999/xhtml -- the examples I have seen so far all have five children, named screenX, screenY, dlientX, clientY, and button, all in the XHTML namespace. Some questions arise. Is this XML representation described somewhere in writing? Are other event properties (type, target element, pageX, pageY, etc.) ever provided? If an element D and one of its ancestors A both have a listener for the same event, the event appears to bubble up from the descendant to the ancestor (at least, in Safari -- I have seen things that say the order of event propagation varies among browsers). Is there a way to signal that a given listener function has handled the event fully (so that the event is not propagated to the other listeners for that event)? Making the listener return true() or false() seemed to have no effect. (But perhaps I am just not very good with sequential functions.) Thanks! -- **************************************************************** * C. M. Sperberg-McQueen, Black Mesa Technologies LLC * http://www.blackmesatech.com * http://cmsmcq.com/mib * http://balisage.net **************************************************************** |