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? ==
* Does the value of the 'fill' property matter for the 'painted' and 'fill' properties? (Yes and no respectively.)
* ...
== Use cases ==
* 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/hidden from the user, while allowing pointer events to be "caught" by parts of the element that are visible to the user.
* Provide a way to allow pointer events to be "caught" by an element even when it is invisible to the user.
== Proposed values ==