Confirmed users, Bureaucrats and Sysops emeriti
969
edits
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 when and which parts of an element can be the target of a pointer event. This document discusses | 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 when and which parts of an element can be the target of a pointer event. This document discusses 'pointer-events', and how it might work in HTML (HTML authors have been asking for 'pointer-events' like functionality since forever). | ||
== 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. | |||
<code> | |||
value areas hit and conditions for a hit | |||
----- ---------------------------------- | |||
auto /* like 'visiblePainted', like 'none' on outer-<svg> */ | |||
visiblePainted fill if(fill:!none), stroke if(stroke:!none), | |||
requires(visibility:visible) | |||
painted fill if(fill:!none), stroke if(stroke:!none) | |||
visible *, require(visibility:visible) | |||
visibleFill fill, requires(visibility:visible) | |||
visibleStroke stroke, requires(visibility:visible) | |||
fill fill | |||
stroke stroke | |||
all * | |||
none - | |||
</code> | |||
== Should clipping affect pointer event targeting? == | == Should clipping affect pointer event targeting? == |