152 Part (Web hosting rating) III .Document Objects Reference Table 15-7
Wednesday, October 31st, 2007152 Part III .Document Objects Reference Table 15-7 (continued) DOMAttrModified mouseout DOMCharacterDataModified mouseover DOMFocusIn mouseup DOMFocusOut reset DOMNodeInserted resize DOMNodeInsertedIntoDocument scroll DOMNodeRemoved select DOMNodeRemovedFromDocument submit DOMSubtreeModified unload Note that the event types specified in the DOM Level 2 are more limited than the wide range of events defined in IE4+. Also, the W3C temporarily tabled the issue of keyboard events until DOM Level 3. Fortunately, Netscape implements keyboard events in a fashion that likely will appear as part of the W3C DOM. The second parameter of the addEventListener()method is a reference to the JavaScript function to be invoked. This is the same form used to assign a function to an event property of an object (for example, objReference.onclick = someFunction), and it should not be a quoted string. This approach also means that you cannot specify parameters in the function call. Therefore, functions that need to reference forms or form control elements must build their own references (with the help of the event object s property that says which object is the event s target). By default, the W3C DOM event model has events bubble upward through the element container hierarchy starting with the target object of the event (for example, the button being clicked). However, if you specify true for the third parameter of the addEventListener() method, event capture is enabled for this particular event type whenever the current object is the event target. This means that any other event type targeted at the current object bubbles upward unless it, too, has an event listener associated with the object and the third parameter is set to true. NN6 does not always set event capture for an element, even when you specify true as the third parameter of addEventListener(). For the most part, you can make do with event bubbling by adding an event listener to a container higher up the element hierarchy. Because event capture is a part of the W3C DOM event model, this feature will likely be implemented in a future version of NN. Using the addEventListener() method requires that the object to which it is attached already exist. Therefore, you most likely will use the method inside an initialization function triggered by the onLoadevent handler for the page. (The document object can use addEventListener()for the load event immediately because the document object exists early in the loading process.) Caution elementObject.addEventListener()
If you are in need for cheap and reliable webhost to host your website, we recommend http web server services.