Event Processing Models
In Netscape, the event is passed as an argument to the handler as in WW_processclick(e)
While in Microsoft IE, event properties are stored in a single window property window.event
So in WW_eventx(e), the argument is ignored in IE
function WW_eventx(e) { // return x value of event
return e.pageX; } // Netscape
else { return window.event.clientX; } // Microsoft
Also there is meant to be a different event handling model in browsers
- In Microsoft IE, events are bubbled up through the containing objects until document is finally reached
- In Netscape4, events are first processed by window and then passed down through container hierarchy. return false stops this sequence
- For both browsers, if you put return false in WW_processclick(e), then clicking on link will NOT load new page