Confirmed users, Bureaucrats and Sysops emeriti
969
edits
SVG:Pointer-events: Difference between revisions
no edit summary
No edit summary |
|||
| Line 32: | Line 32: | ||
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. | ||
== Use cases == | |||
Please only append to this list so that we have consistent numbering so we can refer to cases by number. | |||
# Provide a way to allow pointer events to go "through" an element even when it's visible to the user. | |||
# Provide a way to allow pointer events to go "through" areas of an element that are transparent, clipped/masked out, or otherwise not visible to users/viewers, while allowing pointer events to be "caught" by parts of the element that are visible to users. | |||
# Provide a way to allow pointer events to be "caught" by an element even when it is invisible to the user. | |||
== Should clipping affect pointer event targeting? == | == Should clipping affect pointer event targeting? == | ||
| Line 46: | Line 54: | ||
* Does the value of the 'fill' property matter for the 'painted' and 'fill' properties? (Yes and no respectively.) | * Does the value of the 'fill' property matter for the 'painted' and 'fill' properties? (Yes and no respectively.) | ||
* ... | * ... | ||
== Proposed values == | == Proposed values == | ||