clientX (int | float): The X coordinate in local coordinates.
clientY (int | float): The Y coordinate in local coordinates.
pageX (int | float): The X coordinate relative to the whole document.
pageY (int | float): The Y coordinate relative to the whole document.
screenX (int | float): The X coordinate in global (screen) coordinates.
screenY (int | float): The Y coordinate in global (screen) coordinates.
There seem to be a few more properties hidden in the event, but not all of them (for some unknown reason).
The only way to change that would be creating your own module or asking a feature request and hope igntion does it one day
We’re providing properties of the MouseEvent (not Pointer Event). In looking at the documentation for that event, it seems that although there are indeed offset properties available, those properties are documented as “experimental” and their behavior is “likely to change in the future” (note the beaker). Until they are no longer experimental and we can “guarantee” their behavior, we will not be adding them to Perspective.
That is surely a bug in their documentation since offsetX and offsetY have been part of the MouseEvent spec since 2009 and have been supported in every major browser for over a decade. Even according to MDN’s over definition of “experimental”, a feature of is no longer considered experimental if it is supported in two or more major browsers. I will create a PR to update its status and see what they say.
Also, pageX and pageY are implemented in Perspective and are also listed as experimental.
The (erroneous) experimental status of the properties is irrelevant.
We’re encoding React MouseEvent objects to JSON to send to the backend, and they don’t have offsetX or offsetY properties (for whatever reason):