com.raquo.domtypes.generic.defs.eventProps
Type members
Classlikes
- Type Params
- DomElementTargetEvent
An event that has an Element as
target. This event type has no corresponding type in JS DOM. See our ownTypedTargetEventtrait.- DomFormElementTargetEvent
An event that has an HTMLFormElement as
target. This event type has no corresponding type in JS DOM. See our ownTypedTargetEventtrait.- DomHtmlElementTargetEvent
An event that has an HTMLElement as
target. This event type has no corresponding type in JS DOM. See our ownTypedTargetEventtrait.- DomInputElementTargetEvent
An event that has an HTMLInputElement as
target. This event type has no corresponding type in JS DOM. See our ownTypedTargetEventtrait. - Strictly speaking, this type is not applicable toonInputbecause the latter can be fired on any HTMLElement that hascontentEditablemode enabled. - Similarly foronChangeandonSelect– these could also fire on anHTMLTextAreaElement.- DomInputEvent
DOM InputEvent https://developer.mozilla.org/en-US/docs/Web/API/InputEvent Note: This type is not implemented in scala-js-dom
Keyboard Events - triggered by user actions on the keyboard
Keyboard Events - triggered by user actions on the keyboard
For type param docs see EventPropBuilder
Media Events - triggered by media like videos, images and audio. These apply to all HTML elements, but they are most common in media elements, like
Media Events - triggered by media like videos, images and audio. These apply to all HTML elements, but they are most common in media elements, like
For type param docs see EventPropBuilder
Miscellaneous Events
Miscellaneous Events
For type param docs see EventPropBuilder
Mouse Events: triggered by a mouse, or similar user actions.
Mouse Events: triggered by a mouse, or similar user actions.
- Type Params
- DomElementMouseEvent
A DomMouseEvent that has an Element as
target. This event type has no corresponding type in JS DOM. See our ownTypedTargetEventtrait.
Most of today's web content assumes the user's pointing device will be a mouse. However, since many devices support other types of pointing input devices, such as pen/stylus and touch surfaces, extensions to the existing pointing device event models are needed and pointer events address that need.
Most of today's web content assumes the user's pointing device will be a mouse. However, since many devices support other types of pointing input devices, such as pen/stylus and touch surfaces, extensions to the existing pointing device event models are needed and pointer events address that need.
Pointer events are DOM events that are fired for a pointing device. They are designed to create a single DOM event model to handle pointing input devices such as a mouse, pen/stylus or touch (such as one or more fingers). The pointer is a hardware-agnostic device that can target a specific set of screen coordinates. Having a single event model for pointers can simplify creating Web sites and applications and provide a good user experience regardless of the user's hardware. However, for scenarios when device-specific handling is desired, pointer events defines a property to inspect the device type which produced the event.
The events needed to handle generic pointer input are analogous to mouse events (mousedown/pointerdown, mousemove/pointermove, etc.). Consequently, pointer event types are intentionally similar to mouse event types. Additionally, a pointer event contains the usual properties present in mouse events (client coordinates, target element, button states, etc.) in addition to new properties for other forms of input: pressure, contact geometry, tilt, etc. In fact, the PointerEvent interface inherits all of the MouseEvent's properties thus facilitating migrating content from mouse events to pointer events.
MDN
Window Events
Window Events
For type param docs see EventPropBuilder