SVG:Pointer-events: Difference between revisions

Jump to navigation Jump to search
no edit summary
No edit summary
Line 1: Line 1:
The [http://www.w3.org/TR/SVG11/ SVG specification] introduced the '[http://www.w3.org/TR/SVG11/interact.html#PointerEventsProperty pointer-events]' property to provide SVG authors with more control over which parts of an element can intercept pointer event, and under what conditions. This document discusses 'pointer-events', and how it might work in HTML (HTML authors have been asking for 'pointer-events' like functionality since forever).
The [http://www.w3.org/TR/SVG11/ SVG specification] introduced the '[http://www.w3.org/TR/SVG11/interact.html#PointerEventsProperty pointer-events]' property to provide SVG authors with more control over which parts of an element can intercept pointer event, and under what conditions. This document discusses 'pointer-events', and how it might work in HTML.


== pointer-events in SVG 1.1 ==
== pointer-events in SVG 1.1 ==


The pointer-events property determines which areas of an element can intercept a pointer event, and under what conditions. The following table summarizes the SVG 1.1 values.
The following table summarizes which areas of an SVG element can intercept a pointer event, and under what conditions, for all the values of pointer-events in SVG 1.1, plus 'auto'.


<code>
<code>
Line 31: Line 31:
</code>
</code>


The syntax of the lines in the column on the right might seem like they could be alternative values for pointer-events that users could use. However, they're pretty verbose, and its not clear that authors want a lot of granularity.
The syntax of the lines in the column on the right might seem like they could be alternative values for pointer-events that users could use. However, they're pretty verbose, and its not clear that authors want a lot of granularity (yet).


== Use cases ==
== Use cases ==
Confirmed users, Bureaucrats and Sysops emeriti
969

edits

Navigation menu