org.w3c.dom.events.package.html Maven / Gradle / Ivy
<span class="http"><span class="sql">package.html</span></span>
The org.w3c.dom.events package provides the Java ME DOM Events API subset
defined by JSR 280. The API is derived from the W3 DOM2 Events API
Java bindings source
(http://www.w3.org/TR/2000/REC-DOM-Level-2-Events-20001113/java-binding.zip),
and the DOM3 Events API Java bindings source
(http://www.w3.org/TR/2006/WD-DOM-Level-3-Events-20060413/java-binding.zip).
The initial version of the JSR 280 modifications was published in October
2006.
Complete list of supported event types
JSR 280 supports all event types defined by DOM level 3. The only
exception are event types related to MutationNameEvent which are not supported.
The following table provides a summary of the event types that are
required to be supported by the implementation. All events will
accomplish the capture and target phases, but not all of them will
accomplish the bubbling phase (see also DOM
event flow). Some events are not cancelable
(see Default
actions and cancelable events). Some events will only be
dispatched to a specific set of possible targets, specified using node
types. Contextual information related to the event type is accessible
using DOM interfaces.
type Bubbling phase Cancelable Target node types DOM interface DOMActivate Yes Yes ElementUIEventDOMFocusIn Yes No ElementUIEventDOMFocusOut Yes No ElementUIEventfocus No No ElementUIEventblur No No ElementUIEventtextInput Yes Yes ElementTextEventclick Yes Yes ElementMouseEventmousedown Yes Yes ElementMouseEventmouseup Yes Yes ElementMouseEventmouseover Yes Yes ElementMouseEventmousemove Yes Yes ElementMouseEventmouseout Yes Yes ElementMouseEventkeydown Yes Yes ElementKeyboardEventkeyup Yes Yes ElementKeyboardEventDOMSubtreeModified Yes No Document, DocumentFragment, Element, AttrMutationEventDOMNodeInserted Yes No Element, Attr, Text, Comment, CDATASection, DocumentType, EntityReference, ProcessingInstructionMutationEventDOMNodeRemoved Yes No Element, Attr, Text, Comment, CDATASection, DocumentType, EntityReference, ProcessingInstructionMutationEventDOMNodeRemovedFromDocument No No Element, Attr, Text, Comment, CDATASection, DocumentType, EntityReference, ProcessingInstructionMutationEventDOMNodeInsertedIntoDocument No No Element, Attr, Text, Comment, CDATASection, DocumentType, EntityReference, ProcessingInstructionMutationEventDOMAttrModified Yes No ElementMutationEventDOMCharacterDataModified Yes No Text, Comment, CDATASection, ProcessingInstructionMutationEventload No No Document, ElementEventunload No No Document, ElementEventabort Yes No ElementEventerror Yes No ElementEventselect Yes No ElementEventchange Yes No ElementEventsubmit Yes Yes ElementEventreset Yes Yes ElementEventresize Yes No Document, ElementUIEventscroll Yes No Document, ElementUIEvent
Extracted from the W3C
DOM3 Events specification
The Progress Event 1.0 specification defines the following event types
in addition:
type Bubbling phase Cancelable Target node types DOM interface loadstart No No ElementProgressEventprogress No No ElementProgressEventerror No No ElementProgressEventabort No No ElementProgressEventload No No ElementProgressEvent
Compiled from the W3C
Progress Event 1.0 specification
Clarification: The purpose of listing the possible event
targets here is to say that an implementation of only
DOM Level 3 Events will not dispatch certain event types to certain
event targets unless requested to by a DOM application. These listings
are not meant to otherwise constrain implementations, applications,
or specifications.
As an example, the event load will trigger event listeners attached on Element nodes for that event and on the capture and target phases. This event cannot be cancelled. If an event listener for the load event is attached to a node other than Document or Element nodes, or if it is attached to the bubbling phase only, this event listener cannot be triggered.
The event objects associated with the event types described above
may contain context information. Refer to the description of the DOM
interfaces for further information.