TBD
TBD. Will be defined in conjunction with markrequest, which is covered by ACTION-25, and not yet in the spec.
UIRequestEvents initiate from the element representing the point-of-regard, and are referenced in the Event object's target
property.
For mainstream user agents, the point-of-regard will likely be the element under a pointer (e.g. mouse cursor) or, in the case of keyboard events, the currently focused element (e.g. document.activeElement). Assistive technologies or other alternative inputs may determine another element to be the subject of the user's attention, and initiate events from this new point-of-regard.
Attributes whose DOM property and content attribute values remain in sync. Identical to reflected attributes in HTML.
The closest DOM ancestor to the user's point-of-regard that declares the current event type via the @ui-actions content attribute or uiActions DOM attribute. The Request Event Receiver is referenced in the Event object's receiver
property.
UI Request Events are not initiated by the user agent unless the following are true:
@ui-actions
element.addEventListener()
Some of this definition will need to be massaged and move into the normative sections above defining @ui-actions.
TBD