Implementations for the ReflectableProperties interface/
Events should generally follow the propagation model, but there's some exceptions to that rule. If so, they should override this to return false. In that case, only bubbling event handlers on the target itself and capturing event handlers on the containing window will be called. (That is, dispatch will call sendDirectly instead of doing the normal capture -> target -> bubble process.)
hints as to whether preventDefault will actually do anything. not entirely reliable.
You can mix this into child class to register some boilerplate. It includes the EventString member, a constructor, and implementations of the dynamic get data interfaces.
This is the widget that emitted the event.
Note: likely to be deprecated at some point.
Prevents the default event handler (if there is one) from being called
Stops the event propagation immediately.
This is an internal implementation detail you should not use. It would be private if the language allowed it and it may be removed without notice.
this sends it only to the target. If you want propagation, use dispatch() instead.
this dispatches the element using the capture -> target -> bubble process
Event fired when an Observeable variable changes. You will want to add an event listener referencing the field like widget.addEventListener((scope StateChanged!(Whatever.field) ev) { });