The pointer-events
CSS property sets under what circumstances (if any) a particular graphic element can become the target of mouse events.
When this property is unspecified, the same characteristics of the visiblePainted
value apply to SVG content.
In addition to indicating that the element is not the target of mouse events, the value none
instructs the mouse event to go "through" the element and target whatever is "underneath" that element instead.
/* Keyword values */ pointer-events: auto; pointer-events: none; pointer-events: visiblePainted; /* SVG only */ pointer-events: visibleFill; /* SVG only */ pointer-events: visibleStroke; /* SVG only */ pointer-events: visible; /* SVG only */ pointer-events: painted; /* SVG only */ pointer-events: fill; /* SVG only */ pointer-events: stroke; /* SVG only */ pointer-events: all; /* SVG only */ /* Global values */ pointer-events: inherit; pointer-events: initial; pointer-events: unset;
The pointer-events
property is specified as a single keyword chosen from the list of values below.
auto
pointer-events
property were not specified. In SVG content, this value and the value visiblePainted
have the same effect.none
pointer-events
set to some other value. In these circumstances, mouse events will trigger event listeners on this parent element as appropriate on their way to/from the descendant during the event capture/bubble phases.visiblePainted
visibility
property is set to visible
and when the mouse cursor is over the interior (i.e., 'fill') of the element and the fill
property is set to a value other than none
, or when the mouse cursor is over the perimeter (i.e., 'stroke') of the element and the stroke
property is set to a value other than none
.visibleFill
visibility
property is set to visible
and when the mouse cursor is over the interior (i.e., fill) of the element. The value of the fill
property does not affect event processing.visibleStroke
visibility
property is set to visible
and when the mouse cursor is over the perimeter (i.e., stroke) of the element. The value of the stroke
property does not affect event processing.visible
visibility
property is set to visible
and the mouse cursor is over either the interior (i.e., fill) or the perimeter (i.e., stroke) of the element. The values of the fill
and stroke
do not affect event processing.painted
fill
property is set to a value other than none
, or when the mouse cursor is over the perimeter (i.e., 'stroke') of the element and the stroke
property is set to a value other than none
. The value of the visibility
property does not affect event processing.fill
fill
and visibility
properties do not affect event processing.stroke
stroke
and visibility
properties do not affect event processing.all
fill
, stroke
and visibility
properties do not affect event processing.auto | none | visiblePainted | visibleFill | visibleStroke | visible | painted | fill | stroke | all | inherit
This example disables mouse events (clicking, dragging, hovering, etc.) on all images.
img { pointer-events: none; }
This example disables mouse events on the link to http://example.com.
<ul> <li><a href="https://developer.mozilla.org">MDN</a></li> <li><a href="http://example.com">example.com</a></li> </ul>
a[href="http://example.com"] { pointer-events: none; }
Note that preventing an element from being the target of mouse events by using pointer-events
does not necessarily mean that mouse event listeners on that element cannot or will not be triggered. If one of the element's children has pointer-events
explicitly set to allow that child to be the target of mouse events, then any events targeting that child will pass through the parent as the event travels along the parent chain, and trigger event listeners on the parent as appropriate. Of course any mouse activity at a point on the screen that is covered by the parent but not by the child will not be caught by either the child or the parent (it will go "through" the parent and target whatever is underneath).
Elements with pointer-events: none
will still receive focus through sequential keyboard navigation using the Tab key.
We would like to provide finer grained control (than just auto
and none
) in HTML for which parts of an element will cause it to "catch" mouse events, and when. To help us in deciding how pointer-events
should be further extended for HTML, if you have any particular things that you would like to be able to do with this property, then please add them to the Use Cases section of this wiki page (don't worry about keeping it tidy).
Specification | Status | Comment |
---|---|---|
Scalable Vector Graphics (SVG) 2 The definition of 'pointer-events' in that specification. | Candidate Recommendation | |
Scalable Vector Graphics (SVG) 1.1 (Second Edition) The definition of 'pointer-events' in that specification. | Recommendation | Initial definition |
Initial value | auto |
---|---|
Applies to | all elements |
Inherited | yes |
Media | visual |
Computed value | as specified |
Animation type | discrete |
Canonical order | the unique non-ambiguous order defined by the formal grammar |
Its extension to HTML elements, though present in early drafts of CSS Basic User Interface Module Level 3, has been pushed to its level 4.
Desktop | ||||||
---|---|---|---|---|---|---|
Chrome | Edge | Firefox | Internet Explorer | Opera | Safari | |
Basic support | 1 | 12 | 1.5 | 11 | 9 | 3 |
Applies to HTML elements | 2 | 12 | 3.6 | 11 | 15 | 4 |
Mobile | |||||||
---|---|---|---|---|---|---|---|
Android webview | Chrome for Android | Edge Mobile | Firefox for Android | Opera for Android | iOS Safari | Samsung Internet | |
Basic support | 2 | ? | Yes | ? | ? | ? | ? |
Applies to HTML elements | ? | ? | ? | ? | ? | ? | ? |
pointer-events
visibility
© 2005–2018 Mozilla Developer Network and individual contributors.
Licensed under the Creative Commons Attribution-ShareAlike License v2.5 or later.
https://developer.mozilla.org/en-US/docs/Web/CSS/pointer-events