从W3C的发展时间轴来看, DOM(Document Object Model)的模型可以分为两种, DOM 0 及 DOM 2. 从数字来看就可以知道DOM 0 当然是比较旧的协议, 我们可以从以下的表格来看:
DOM1 协定:
Event Name |
Description |
onblur() |
The element has lost focus (that is, it is not selected by the user). |
onchange0 |
The element has either changed (such as by typing into a text field) or the element has lost focus. |
onclick0 |
The mouse has been clicked on an element. |
ondblclick() |
The mouse has been double-clicked on an element. |
onfocus() |
The element has gotten focus. |
onkeydown() |
A keyboard key has been pressed down (as opposed to released) while the element has focus. |
onkeypress() |
A keyboard key has been pressed while the element has focus. |
onkeyup() |
A keyboard key has been released while the element has focus. |
onload() |
The element has loaded (document, frameset, or image). |
onmousedown() |
A mouse button has been pressed. |
onmousemove() |
The mouse has been moved. |
onmouseout() |
The mouse has been moved off of or away from an element. |
onmouseover() |
The mouse has moved over an element. |
onmouseup() |
A mouse button has been released. |
onreset() |
The form element has been reset, such as when a form reset button is pressed. |
onresize() |
The window's size has been changed. |
onselect() |
The text of a form element has been selected. |
onsubmit() |
The form has been submitted. |
onunload() |
The document or frameset has been unloaded. |
DOM2 的进化:
DOM 0 Event |
DOM 2 Event |
onblur() |
blur |
onfocus() |
focus |
onchange() |
change |
onmouseover() |
mouseover |
onmouseout() |
mouseout |
onmousemove() |
mousemove |
onmousedown() |
mousedown |
onmouseup() |
mouseup |
onclick() |
click |
ondblclick() |
dblclick |
onkeydown() |
keydown |
onkeyup() |
keyup |
onkeypress() |
keypress |
onsubmit() |
submit |
onload() |
load |
onunload() |
unload |
The new DOM2 usage can be observed with the addEventListener() function:
addEventListener(event,function,capture/bubble);
The parameter event is as shown in the table above. Function is the function to be executed. Capture and bubble are two time modes formulated by W3C. Simply put, capture is to read the last line from the beginning of the document and then execute the event, while bubble It first searches for the specified location and then executes the event.
The parameter of capture/bubble is a Boolean value, True means capture, False means bubble. Windows Internet Explorer also has an EventHandler, which is attachEvent(), and the format is as follows:
window.attachEvent("submit",myFunction());
What is special is that attachEvent does not need to specify the capture/bubble parameters, because Bubble mode is used in the Windows IE environment. Here is an image Rollover example to show the usage of the event:
“http://www.w3.org/TR/html4/strict.dtd ">
alt=”Home”>
alt=”About”>
alt =”Blog”>
The above typeof window.addEventListener != “undefined” program code can determine whether the user’s browser supports the AddEventListener event model. If not, use attachEvent.
W3C and IE both support removing specified events. The purpose is to remove set events. The formats are as follows:
W3C format:
removeEventListener(event,function,capture/bubble);
The format of Windows IE is as follows:
detachEvent(event,function);
Data reference: Chapter 14 - Browsers and JavaScript, JavaScript Step by Step, by Steve Suehring