--- title: click slug: Web/API/Element/click_event tags: - 待翻譯 translation_of: Web/API/Element/click_event ---
click
事件通常會在設備的按鈕(通常是滑鼠按鍵)點擊元素時執行。
Property | Type | Description |
---|---|---|
target {{readonlyInline}} |
EventTarget |
The event target (the topmost target in the DOM tree). |
type {{readonlyInline}} |
DOMString |
The type of event. |
bubbles {{readonlyInline}} |
Boolean |
Whether the event normally bubbles or not |
cancelable {{readonlyInline}} |
Boolean |
Whether the event is cancellable or not? |
view {{readonlyInline}} |
WindowProxy |
document.defaultView (window of the document) |
detail {{readonlyInline}} |
long (float ) |
A count of consecutive clicks that happened in a short amount of time, incremented by one. |
currentTarget {{readonlyInline}} |
EventTarget | The node that had the event listener attached. |
relatedTarget {{readonlyInline}} |
EventTarget | For mouseover , mouseout , mouseenter and mouseleave events: the target of the complementary event (the mouseleave target in the case of a mouseenter event). null otherwise. |
screenX {{readonlyInline}} |
long | The X coordinate of the mouse pointer in global (screen) coordinates. |
screenY {{readonlyInline}} |
long | The Y coordinate of the mouse pointer in global (screen) coordinates. |
clientX {{readonlyInline}} |
long | The X coordinate of the mouse pointer in local (DOM content) coordinates. |
clientY {{readonlyInline}} |
long | The Y coordinate of the mouse pointer in local (DOM content) coordinates. |
button {{readonlyInline}} |
unsigned short | The button number that was pressed when the mouse event was fired: Left button=0, middle button=1 (if present), right button=2. For mice configured for left handed use in which the button actions are reversed the values are instead read from right to left. |
buttons {{readonlyInline}} |
unsigned short | The buttons being pressed when the mouse event was fired: Left button=1, Right button=2, Middle (wheel) button=4, 4th button (typically, "Browser Back" button)=8, 5th button (typically, "Browser Forward" button)=16. If two or more buttons are pressed, returns the logical sum of the values. E.g., if Left button and Right button are pressed, returns 3 (=1 | 2). More info. |
mozPressure {{readonlyInline}} |
float | The amount of pressure applied to a touch or tabdevice when generating the event; this value ranges between 0.0 (minimum pressure) and 1.0 (maximum pressure). |
ctrlKey {{readonlyInline}} |
boolean | true if the control key was down when the event was fired. false otherwise. |
shiftKey {{readonlyInline}} |
boolean | true if the shift key was down when the event was fired. false otherwise. |
altKey {{readonlyInline}} |
boolean | true if the alt key was down when the event was fired. false otherwise. |
metaKey {{readonlyInline}} |
boolean | true if the meta key was down when the event was fired. false otherwise. |
<div id="test"></div> <script> document.getElementById("test").addEventListener("click", function( event ) { // 在 “clicked div”顯示點擊次數 event.target.innerHTML = "click count: " + event.detail; }, false); </script>
Internet Explorer 8 & 9 suffer from a bug where elements with a computed {{cssxref("background-color")}} of transparent
that are overlaid on top of other element(s) won't receive click
events. Any click
events will be fired at the underlying element(s) instead. See this live example for a demonstration.
Known workarounds for this bug:
{{cssxref("background-color")}}: rgba(0,0,0,0)
{{cssxref("opacity")}}: 0
and an explicit {{cssxref("background-color")}} other than transparent
filter: alpha(opacity=0);
and an explicit {{cssxref("background-color")}} other than transparent
Safari Mobile 7.0+ (and likely earlier versions too) suffers from a bug where click
events aren't fired on elements that aren't typically interactive (e.g. {{HTMLElement("div")}}) and which also don't have event listeners directly attached to the elements themselves (i.e. event delegation is being used). See this live example for a demonstration. See also Safari's docs on making elements clickable and the definition of "clickable element".
Known workarounds for this bug:
: pointer;
on the element or any of its ancestors.onclick=""
attribute to the element or any of its ancestors up to but not including {{HTMLElement("body")}}.click
event delegation.Safari Mobile considers the following elements to be typically interactive (and thus they aren't affected by this bug):
href
)href
)