-path: sections/event-types.include -
path: sections/event-uievent.include@@ -141,7 +137,6 @@ path: sections/event-keyboardevent.include
path: sections/event-compositionevent.include-
diff --git a/sections/event-compositionevent.txt b/sections/event-compositionevent.txt index d7fda0a..db14211 100644 --- a/sections/event-compositionevent.txt +++ b/sections/event-compositionevent.txt @@ -1,3 +1,4 @@ +diff --git a/sections/event-focusevent.txt b/sections/event-focusevent.txt index ef6b46a..f54a5d3 100644 --- a/sections/event-focusevent.txt +++ b/sections/event-focusevent.txt @@ -1,3 +1,4 @@ + Composition Events
Composition Events provide a means for inputing text in a supplementary or @@ -343,3 +344,4 @@ is closed, minimized, switched out of focus, or otherwise dismissed, and the focus switched back to the user agent). +diff --git a/sections/event-inputevent.txt b/sections/event-inputevent.txt index 7153a6c..86e9215 100644 --- a/sections/event-inputevent.txt +++ b/sections/event-inputevent.txt @@ -1,3 +1,4 @@ + Focus Events
@@ -251,3 +252,4 @@ focus. The [=blur=] event MUST fire before the dispatch of this event type. This event type is similar to [=blur=], but does bubble. +
diff --git a/sections/event-keyboardevent.txt b/sections/event-keyboardevent.txt index bf2547a..3e7c33c 100644 --- a/sections/event-keyboardevent.txt +++ b/sections/event-keyboardevent.txt @@ -1,3 +1,4 @@ + Input Events
Input events are sent as notifications whenever the DOM is being updated (or about @@ -166,3 +167,4 @@ DOM has been updated. +diff --git a/sections/event-mouseevent.txt b/sections/event-mouseevent.txt index 93506f4..2d923ba 100644 --- a/sections/event-mouseevent.txt +++ b/sections/event-mouseevent.txt @@ -1,3 +1,4 @@ + Keyboard Events
Keyboard events are device dependent, i.e., they rely on the capabilities of @@ -593,3 +594,4 @@ character value. +diff --git a/sections/event-types.txt b/sections/event-types.txt deleted file mode 100644 index 2e3cf46..0000000 --- a/sections/event-types.txt +++ /dev/null @@ -1,10 +0,0 @@ - Mouse Events
The mouse event module originates from the [[HTML401]]onclick, @@ -2012,3 +2013,4 @@ myDiv.addEventListener("auxclick", function(e) { drag operation with a mouse button pressed. +Event Types
- - -The DOM Event Model allows a DOM implementation to support multiple modules of -events. The model has been designed to allow addition of new event modules in -the future. This document does not attempt to define all possible events. For -purposes of interoperability, the DOM defines a module of user interface events -including lower level device dependent events and a module of document mutation -events. - diff --git a/sections/event-uievent.txt b/sections/event-uievent.txt index 2116542..ca422ef 100644 --- a/sections/event-uievent.txt +++ b/sections/event-uievent.txt @@ -1,3 +1,4 @@ +diff --git a/sections/event-wheelevent.txt b/sections/event-wheelevent.txt index f371fbb..0c773e8 100644 --- a/sections/event-wheelevent.txt +++ b/sections/event-wheelevent.txt @@ -1,3 +1,4 @@ + User Interface Events
The User Interface event module contains basic event types associated with @@ -271,3 +272,4 @@ controls, or image or markup selections such as in SVG. +diff --git a/sections/glossary.txt b/sections/glossary.txt index f2a8096..2b0cf6e 100644 --- a/sections/glossary.txt +++ b/sections/glossary.txt @@ -225,8 +225,8 @@ the definitions for more information. characteristics which distinguish it from other event types. For example, the EVENT{click} event type has different characteristics than the EVENT{mouseover} or EVENT{load} event types. The event type is exposed as - the {{Event/type}} attribute on the event object. See [[#event-types]] for - more details. Also loosely referred to as "event", such as the + the {{Event/type}} attribute on the event object. + Also loosely referred to as "event", such as the EVENT{click} event. : fire diff --git a/sections/introduction.txt b/sections/introduction.txt index 29cf73f..799edbf 100644 --- a/sections/introduction.txt +++ b/sections/introduction.txt @@ -76,7 +76,7 @@ type have been met. A browser conforms specifically to UI Events if it implements the - interfaces and related event types specified in [[#event-types]]. + interfaces and related event types specified in this document. A conforming browser MUST support scripting, declarative interactivity, or some other means of detecting and dispatching events in the manner @@ -147,7 +147,7 @@ A specification or host language conforms specifically to UI Events if it references and uses the interfaces and related event - types specified in [[#event-types]]. A conforming specification MAY + types specified in this document. A conforming specification MAY define additional interfaces and event types appropriate to that specification, or MAY extend the UI Events interfaces and event types in a manner that does not contradict or conflict with the Wheel Events
Wheels are devices that can be rotated in one or more spatial dimensions, and which can be associated with a pointer device. The coordinate system depends on the @@ -308,3 +309,4 @@ +