Protected altProtected buttonProtected buttonsProtected clientXDataProtected clientYDataProtected ctrlProtected currentProtected metaProtected movementXDataProtected movementYDataProtected offsetXDataProtected offsetYDataProtected pageXDataProtected pageYDataProtected relatedProtected screenXDataProtected screenYDataProtected shiftProtected targetProtected timeTrue if the alt key was down when the mouse event was fired.
The button number that was pressed (if applicable) when the mouse event was fired.
The buttons being depressed (if any) when the mouse event was fired.
The X coordinate of the mouse pointer in local (DOM content) coordinates.
The Y coordinate of the mouse pointer in local (DOM content) coordinates.
True if the control key was down when the mouse event was fired.
A reference to the currently registered target for the event. This is the object to which the event is currently slated to be sent. It's possible this has been changed along the way through retargeting.
True if the meta key was down when the mouse event was fired.
The X coordinate of the mouse pointer relative to the position of the last mousemove event.
The Y coordinate of the mouse pointer relative to the position of the last mousemove event.
The X coordinate of the mouse pointer relative to the position of the padding edge of the target node.
The Y coordinate of the mouse pointer relative to the position of the padding edge of the target node.
The X coordinate of the mouse pointer relative to the whole document.
The Y coordinate of the mouse pointer relative to the whole document.
The secondary target for the event, if there is one.
The X coordinate of the mouse pointer in global (screen) coordinates.
The Y coordinate of the mouse pointer in global (screen) coordinates.
True if the shift key was down when the mouse event was fired.
A reference to the target to which the event was originally dispatched.
The time at which the event was created (in milliseconds). By specification, this value is time since epoch—but in reality, browsers' definitions vary. In addition, work is underway to change this to be a DOMHighResTimeStamp instead.
Generated using TypeDoc
Single point interaction data implementation with write accesses.