-path: sections/changes.include --
path: sections/acknowledgements.include diff --git a/sections/changes.txt b/sections/changes.txt deleted file mode 100644 index 60b8200..0000000 --- a/sections/changes.txt +++ /dev/null @@ -1,135 +0,0 @@ -- diff --git a/sections/legacy-event-initializers.txt b/sections/legacy-event-initializers.txt index 207f2a2..8545fa7 100644 --- a/sections/legacy-event-initializers.txt +++ b/sections/legacy-event-initializers.txt @@ -205,7 +205,7 @@ described in this Appendix.Changes
- - -Changes between DOM Level 2 Events and UI Events
- - Numerous clarifications to the interfaces and event types have been made. - TheHTMLEventsmodule is no longer defined in this document. - The EVENT{focus} and EVENT{blur} events have been added to the {{UIEvent}} - module, and the EVENT{dblclick} event has been added to the {{MouseEvent}} - module. This new specification provides a better separation between the DOM - event flow, the event types, and the DOM interfaces. - -Changes to DOM Level 2 event flow
- - This new specification introduced the following new concepts in the - event flow: - - * Event listeners are now ordered. In DOM Level 2, the event ordering - was unspecified. - * The event flow now includes theWindow, to - reflect existing implementations. - -Changes to DOM Level 2 event types
- - Many clarifications have been made on the event types. The conformance - is now explicitly defined against the event types, and not only in terms - of interfaces used by the event types. - -"MutationEvents"have been deprecated. Support for - namespaced events, present in early drafts of this specification, has - also been removed. - - For user agents which support the EVENT{DOMNodeInserted} and - EVENT{DOMNodeRemoved} event types, this specification no longer requires - that the event type be fired forAttrnodes. - - Theresizeevent type no longer bubbles and the EVENT{mousemove} - event is now cancelable, reflecting existing implementations. - -Changes to DOM Level 2 Events interfaces
- --
- -- Interface {{Event}}
-- - * The {{Event}} interface has one new attribute, - {{Event/defaultPrevented}}, and one new method, - {{Event/stopImmediatePropagation()}}. - * {{Event/timeStamp}} is now a
- -Numberin the - ECMAScript binding. A proposed correction to make the same - change in [[DOM-Level-3-Core]] is forthcoming. - * This specification considers the {{Event/type}} attribute - to be case-sensitive, while DOM Level 2 Events considers - {{Event/type}} to be case-insensitive. -- Interface {{EventTarget}}
-- - * The method {{EventTarget/dispatchEvent()}} was modified. -
- -- Interface {{MouseEvent}}
-- - * The {{MouseEvent}} interface has one new method {{MouseEvent/getModifierState()}}. -
- -- Exception
-EventException- - * The exception
-EventExceptionis removed in this - specification. The priorDISPATCH_REQUEST_ERR- code is re-mapped to aDOMExceptionof type -InvalidStateError. -New Interfaces
- - The interfaces {{CustomEvent}}, {{FocusEvent}}, {{KeyboardEvent}}, - {{CompositionEvent}}, and {{WheelEvent}} were added to the Events module. - -Changes between different drafts of UI Events
- - The DOM Level 3 Events document was originally developed between 2000 and - 2003, and published as a W3C Note, pending further feedback and interest - from implementers. In 2006, it was picked up for revision and progress on - the Recommendation Track, and was then revised to reflect the current state - of implementation and the needs of script authors. - - Despite its status only as a W3C Note, rather than an official - Recommendation, DOM 3 Events saw some implementation, and was also - referenced by other specifications, so care is being taken to cause minimal - disruption, while still adapting the specification to the current - environment. - - The current specification has been reordered significantly from the earlier - W3C Note form, and also from the structure of DOM2 Events, in order to - clarify the material. New diagrams have been put in place to represent - hierarchies and events flows more clearly. Here are some of the more - important changes between drafts: - - * Thekey identifierfeature has been renamedkey valueto - disambiguate them from unique identifiers for keys. - - * The {{KeyboardEvent}} interface was briefly (from 2003-2010) defined to - havekeyIdentifierandkeyLocationattributes, - but these were removed in favor of the current {{KeyboardEvent/key}} and - {{KeyboardEvent/location}} attributes. These attributes were not widely - implemented. - - * The {{KeyboardEvent}} and {{CompositionEvent}} interfaces defined a -localeattribute. This attribute was underspecified and - moved into a technical note until it can be specified adequately. - Refer to this - old version of UI Events - (before the DOM3Events spec was renamed "UI Events") for details. - - * The {{KeyboardEvent}} also had acharattribute that - was only used by the EVENT{keypress} event. Since the keypress event has - been deprecated, this attribute was no longer useful and was removed. - - * Thechange,submit, andreset- events were removed, since they were specific to HTML forms, and are - specified in [[HTML5]]. - - * ThetextInputevent, originally proposed as a replacement - for EVENT{keypress}, was removed in favor of the current - EVENT{beforeinput} and EVENT{input} events. - - * Namespaced events have been removed. - - * Updated to use [[WebIDL]]. - - * EventException has been removed. - -The argument list to this legacy KeyboardEvent initializer does not include the
@@ -296,7 +296,7 @@ described in this Appendix.detailArg(present in other initializers) and - adds thelocaleargument (see [[#changes-drafts]]); it is + adds thelocaleargument; it is necessary to preserve this inconsistency for compatibility with existing implementations.The argument list to this legacy CompositionEvent initializer does not include the
detailArg(present in other initializers) and - adds thelocaleargument (see [[#changes-drafts]]); it is + adds thelocaleargument; it is necessary to preserve this inconsistency for compatibility with existing implementations.