Return composedPath. diff --git a/dom.html b/dom.html index 85318c3db..254b509f5 100644 --- a/dom.html +++ b/dom.html @@ -71,7 +71,7 @@
DOM
-Living Standard — Last Updated
+Living Standard — Last Updated
-
@@ -419,11 +419,11 @@
-
-
If currentTarget is a node and tuple’s item is not closed-shadow-hidden from currentTarget, or currentTarget is not a node, then append tuple’s item to composedPath.
+If currentTarget is a
+Windowobject, then:-
+
-
+
If tuple’s item is not a node, or tuple’s item is not closed-shadow-hidden from tuple’s item’s shadow-including root, then append tuple’s item to composedPath.
+
-
+
-
+
Otherwise if currentTarget is a node and tuple’s item is not closed-shadow-hidden from currentTarget, or currentTarget is + not a node, then append tuple’s item to composedPath.
-
Return composedPath.
@@ -674,7 +681,7 @@composed. It has to be supported for legacy content.
3.3. Interface
CustomEvent[Constructor(DOMString type, optional CustomEventInit eventInitDict), - Exposed=(Window,Worker)] + Exposed=(Window,Worker)] interface CustomEvent : Event { readonly attribute any detail; @@ -729,7 +736,7 @@
Event interface that have such a method only have it for historical reasons. 3.6. Interface
-EventTarget[Exposed=(Window,Worker)] +
[Exposed=(Window,Worker)] interface EventTarget { void addEventListener(DOMString type, EventListener? callback, optional (AddEventListenerOptions or boolean) options); void removeEventListener(DOMString type, EventListener? callback, optional (EventListenerOptions or boolean) options); @@ -816,7 +823,7 @@
The
addEventListener(type, callback, options)method, when invoked, must run these steps:-
-
If context object’s relevant global object is a
+ServiceWorkerGlobalScopeobject and its associated service worker’s script resource’s has ever been evaluated flag is set, then throw aTypeError. [SERVICE-WORKERS]If context object’s relevant global object is a
ServiceWorkerGlobalScopeobject and its associated service worker’s script resource’s has ever been evaluated flag is set, then throw aTypeError. [SERVICE-WORKERS]To optimize storing the event types allowed for the service worker and to avoid non-deterministic changes to the event listeners, invocation of the method is allowed only during the very first evaluation of the service worker script.
@@ -831,7 +838,7 @@The
removeEventListener(type, callback, options)method, when invoked, must, run these steps-
-
If context object’s relevant global object is a
+ServiceWorkerGlobalScopeobject and its associated service worker’s script resource’s has ever been evaluated flag is set, then throw aTypeError. [SERVICE-WORKERS]If context object’s relevant global object is a
ServiceWorkerGlobalScopeobject and its associated service worker’s script resource’s has ever been evaluated flag is set, then throw aTypeError. [SERVICE-WORKERS] -
Let capture be the result of flattening options.
-
@@ -1008,7 +1015,7 @@
If listener’s passive is true, set event’s in passive listener flag.
- -
Call a user object’s operation with listener’s callback, +
Call a user object’s operation with listener’s callback, "
handleEvent", a list of arguments consisting of event, and event’scurrentTargetattribute value as the callback this value. If this throws an exception, report the exception.- @@ -1047,10 +1054,10 @@
Each such document is represented as a node tree. Some of the nodes in a tree can have children, while others are always leaves.
To illustrate, consider this HTML document:
<!DOCTYPE html> -<html class=e> - <head><title>Aliens?</title></head> - <body>Why yes.</body> -</html> +<html class=e> + <head><title>Aliens?</title></head> + <body>Why yes.</body> +</html>
It is represented as follows:
-
@@ -1502,8 +1509,8 @@
4.2.4. Mixin
NonElementParentNodeWeb compatibility prevents the
-getElementById()method from being exposed on elements (and therefore onParentNode).[NoInterfaceObject, - Exposed=Window] +
[NoInterfaceObject, + Exposed=Window] interface NonElementParentNode { Element? getElementById(DOMString elementId); }; @@ -1518,8 +1525,8 @@
getElementById(elementId)method, when invoked, must return the first element, in tree order, within context object’s descendants, whose ID is elementId, and null if there is no such element otherwise.4.2.5. Mixin
-DocumentOrShadowRoot[NoInterfaceObject, - Exposed=Window] +
[NoInterfaceObject, + Exposed=Window] interface DocumentOrShadowRoot { }; Document implements DocumentOrShadowRoot; @@ -1543,19 +1550,19 @@
Return node.
- -
[NoInterfaceObject, - Exposed=Window] +
[NoInterfaceObject, + Exposed=Window] interface ParentNode { - [SameObject] readonly attribute HTMLCollection children; + [SameObject] readonly attribute HTMLCollection children; readonly attribute Element? firstElementChild; readonly attribute Element? lastElementChild; readonly attribute unsigned long childElementCount; - [CEReactions, Unscopable] void prepend((Node or DOMString)... nodes); - [CEReactions, Unscopable] void append((Node or DOMString)... nodes); + [CEReactions, Unscopable] void prepend((Node or DOMString)... nodes); + [CEReactions, Unscopable] void append((Node or DOMString)... nodes); Element? querySelector(DOMString selectors); - [NewObject] NodeList querySelectorAll(DOMString selectors); + [NewObject] NodeList querySelectorAll(DOMString selectors); }; Document implements ParentNode; DocumentFragment implements ParentNode; @@ -1612,8 +1619,8 @@
The
querySelectorAll(selectors)method, when invoked, must return the static result of running scope-match a selectors string selectors against context object.4.2.7. Mixin
NonDocumentTypeChildNodeWeb compatibility prevents the
-previousElementSiblingandnextElementSiblingattributes from being exposed on doctypes (and therefore onChildNode).[NoInterfaceObject, - Exposed=Window] +
[NoInterfaceObject, + Exposed=Window] interface NonDocumentTypeChildNode { readonly attribute Element? previousElementSibling; readonly attribute Element? nextElementSibling; @@ -1634,13 +1641,13 @@
following sibling that is an element, and null otherwise.
4.2.8. Mixin
-ChildNode[NoInterfaceObject, - Exposed=Window] +
[NoInterfaceObject, + Exposed=Window] interface ChildNode { - [CEReactions, Unscopable] void before((Node or DOMString)... nodes); - [CEReactions, Unscopable] void after((Node or DOMString)... nodes); - [CEReactions, Unscopable] void replaceWith((Node or DOMString)... nodes); - [CEReactions, Unscopable] void remove(); + [CEReactions, Unscopable] void before((Node or DOMString)... nodes); + [CEReactions, Unscopable] void after((Node or DOMString)... nodes); + [CEReactions, Unscopable] void replaceWith((Node or DOMString)... nodes); + [CEReactions, Unscopable] void remove(); }; DocumentType implements ChildNode; Element implements ChildNode; @@ -1721,8 +1728,8 @@
Remove the context object from context object’s parent.
-
-
4.2.9. Mixin:
-Slotable[NoInterfaceObject, - Exposed=Window] +
[NoInterfaceObject, + Exposed=Window] interface Slotable { readonly attribute HTMLSlotElement? assignedSlot; }; @@ -1745,7 +1752,7 @@
collection must be sorted in tree order.
4.2.10.1. Interface
NodeListA
-NodeListobject is a collection of nodes.[Exposed=Window] +
[Exposed=Window] interface NodeList { getter Node? item(unsigned long index); readonly attribute unsigned long length; @@ -1769,7 +1776,7 @@
-
-
3. 3.1. Introduction to "DOM Events"
Throughout the web platform events are dispatched to objects to signal an
occurrence, such as network activity or user interaction. These objects implement the EventTarget interface and can therefore add event listeners to observe events by calling addEventListener():
-obj.addEventListener("load", imgFetched)
+obj.addEventListener("load", imgFetched)
-function imgFetched(ev) {
- // great success
- …
+function imgFetched(ev) {
+ // great success
+ …
}
Event listeners can be removed
@@ -434,12 +434,12 @@
event was dispatched (obj above).
Now while typically events are dispatched by the user agent
as the result of user interaction or the completion of some task, applications can dispatch events themselves, commonly known as synthetic events:
-// add an appropriate event listener
-obj.addEventListener("cat", function(e) { process(e.detail) })
+// add an appropriate event listener
+obj.addEventListener("cat", function(e) { process(e.detail) })
-// create and dispatch the event
-var event = new CustomEvent("cat", {"detail":{"hazcheeseburger":true}})
-obj.dispatchEvent(event)
+// create and dispatch the event
+var event = new CustomEvent("cat", {"detail":{"hazcheeseburger":true}})
+obj.dispatchEvent(event)
Apart from signaling, events are
sometimes also used to let an application control what happens next in an
@@ -448,9 +448,9 @@
events dispatched by the application
(synthetic events) can make use of the return value of the dispatchEvent() method:
-if(obj.dispatchEvent(event)) {
- // event was not canceled, time for some magic
- …
+if(obj.dispatchEvent(event)) {
+ // event was not canceled, time for some magic
+ …
}
When an event is dispatched to an object that participates in a tree (e.g. an element), it can reach event listeners on that object’s ancestors too. First all object’s ancestor event listeners whose capture variable is set to true are invoked, in tree order. Second, object’s own event listeners are invoked. And
@@ -459,23 +459,23 @@
tree order.
Lets look at an example of how events work in a tree:
<!doctype html>
-<html>
- <head>
- <title>Boring example</title>
- </head>
- <body>
- <p>Hello <span id=x>world</span>!</p>
- <script>
- function test(e) {
- debug(e.target, e.currentTarget, e.eventPhase)
+<html>
+ <head>
+ <title>Boring example</title>
+ </head>
+ <body>
+ <p>Hello <span id=x>world</span>!</p>
+ <script>
+ function test(e) {
+ debug(e.target, e.currentTarget, e.eventPhase)
}
- document.addEventListener("hey", test, {capture: true})
- document.body.addEventListener("hey", test)
- var ev = new Event("hey", {bubbles:true})
- document.getElementById("x").dispatchEvent(ev)
- </script>
- </body>
-</html>
+ document.addEventListener("hey", test, {capture: true})
+ document.body.addEventListener("hey", test)
+ var ev = new Event("hey", {bubbles:true})
+ document.getElementById("x").dispatchEvent(ev)
+ </script>
+ </body>
+</html>
The debug function will be invoked twice. Each time the event’s target attribute value will be the span element. The
first time currentTarget attribute’s
@@ -486,7 +486,7 @@
AT_TARGET.
3.2. Interface Event
[Constructor(DOMString type, optional EventInit eventInitDict),
- Exposed=(Window,Worker)]
+ Exposed=(Window,Worker)]
interface Event {
readonly attribute DOMString type;
readonly attribute EventTarget? target;
@@ -508,7 +508,7 @@ readonly attribute boolean defaultPrevented;
readonly attribute boolean composed;
- [Unforgeable] readonly attribute boolean isTrusted;
+ [Unforgeable] readonly attribute boolean isTrusted;
readonly attribute DOMTimeStamp timeStamp;
void initEvent(DOMString type, boolean bubbles, boolean cancelable); // historical
@@ -592,7 +592,14 @@ context object’s path:
EventTarget interface and can therefore add event listeners to observe events by calling addEventListener():obj.addEventListener("load", imgFetched)
-function imgFetched(ev) {
- // great success
- …
+function imgFetched(ev) {
+ // great success
+ …
}
Event listeners can be removed @@ -434,12 +434,12 @@
event was dispatched (obj above).
Now while typically events are dispatched by the user agent
as the result of user interaction or the completion of some task, applications can dispatch events themselves, commonly known as synthetic events:
-// add an appropriate event listener
-obj.addEventListener("cat", function(e) { process(e.detail) })
+// add an appropriate event listener
+obj.addEventListener("cat", function(e) { process(e.detail) })
-// create and dispatch the event
-var event = new CustomEvent("cat", {"detail":{"hazcheeseburger":true}})
-obj.dispatchEvent(event)
+// create and dispatch the event
+var event = new CustomEvent("cat", {"detail":{"hazcheeseburger":true}})
+obj.dispatchEvent(event)
Apart from signaling, events are
sometimes also used to let an application control what happens next in an
@@ -448,9 +448,9 @@
events dispatched by the application
(synthetic events) can make use of the return value of the dispatchEvent() method:
-if(obj.dispatchEvent(event)) {
- // event was not canceled, time for some magic
- …
+if(obj.dispatchEvent(event)) {
+ // event was not canceled, time for some magic
+ …
}
When an event is dispatched to an object that participates in a tree (e.g. an element), it can reach event listeners on that object’s ancestors too. First all object’s ancestor event listeners whose capture variable is set to true are invoked, in tree order. Second, object’s own event listeners are invoked. And
@@ -459,23 +459,23 @@
tree order.
Lets look at an example of how events work in a tree:
<!doctype html>
-<html>
- <head>
- <title>Boring example</title>
- </head>
- <body>
- <p>Hello <span id=x>world</span>!</p>
- <script>
- function test(e) {
- debug(e.target, e.currentTarget, e.eventPhase)
+<html>
+ <head>
+ <title>Boring example</title>
+ </head>
+ <body>
+ <p>Hello <span id=x>world</span>!</p>
+ <script>
+ function test(e) {
+ debug(e.target, e.currentTarget, e.eventPhase)
}
- document.addEventListener("hey", test, {capture: true})
- document.body.addEventListener("hey", test)
- var ev = new Event("hey", {bubbles:true})
- document.getElementById("x").dispatchEvent(ev)
- </script>
- </body>
-</html>
+ document.addEventListener("hey", test, {capture: true})
+ document.body.addEventListener("hey", test)
+ var ev = new Event("hey", {bubbles:true})
+ document.getElementById("x").dispatchEvent(ev)
+ </script>
+ </body>
+</html>
The debug function will be invoked twice. Each time the event’s target attribute value will be the span element. The
first time currentTarget attribute’s
@@ -486,7 +486,7 @@
AT_TARGET.
3.2. Interface Event
[Constructor(DOMString type, optional EventInit eventInitDict),
- Exposed=(Window,Worker)]
+ Exposed=(Window,Worker)]
interface Event {
readonly attribute DOMString type;
readonly attribute EventTarget? target;
@@ -508,7 +508,7 @@ readonly attribute boolean defaultPrevented;
readonly attribute boolean composed;
- [Unforgeable] readonly attribute boolean isTrusted;
+ [Unforgeable] readonly attribute boolean isTrusted;
readonly attribute DOMTimeStamp timeStamp;
void initEvent(DOMString type, boolean bubbles, boolean cancelable); // historical
@@ -592,7 +592,14 @@ context object’s path:
Now while typically events are dispatched by the user agent as the result of user interaction or the completion of some task, applications can dispatch events themselves, commonly known as synthetic events:
-// add an appropriate event listener -obj.addEventListener("cat", function(e) { process(e.detail) }) +// add an appropriate event listener +obj.addEventListener("cat", function(e) { process(e.detail) }) -// create and dispatch the event -var event = new CustomEvent("cat", {"detail":{"hazcheeseburger":true}}) -obj.dispatchEvent(event) +// create and dispatch the event +var event = new CustomEvent("cat", {"detail":{"hazcheeseburger":true}}) +obj.dispatchEvent(event)Apart from signaling, events are sometimes also used to let an application control what happens next in an @@ -448,9 +448,9 @@
events dispatched by the application (synthetic events) can make use of the return value of the dispatchEvent()method: -if(obj.dispatchEvent(event)) { - // event was not canceled, time for some magic - … +if(obj.dispatchEvent(event)) { + // event was not canceled, time for some magic + … }When an event is dispatched to an object that participates in a tree (e.g. an element), it can reach event listeners on that object’s ancestors too. First all object’s ancestor event listeners whose capture variable is set to true are invoked, in tree order. Second, object’s own event listeners are invoked. And @@ -459,23 +459,23 @@
tree order. Lets look at an example of how events work in a tree:
<!doctype html> -<html> - <head> - <title>Boring example</title> - </head> - <body> - <p>Hello <span id=x>world</span>!</p> - <script> - function test(e) { - debug(e.target, e.currentTarget, e.eventPhase) +<html> + <head> + <title>Boring example</title> + </head> + <body> + <p>Hello <span id=x>world</span>!</p> + <script> + function test(e) { + debug(e.target, e.currentTarget, e.eventPhase) } - document.addEventListener("hey", test, {capture: true}) - document.body.addEventListener("hey", test) - var ev = new Event("hey", {bubbles:true}) - document.getElementById("x").dispatchEvent(ev) - </script> - </body> -</html> + document.addEventListener("hey", test, {capture: true}) + document.body.addEventListener("hey", test) + var ev = new Event("hey", {bubbles:true}) + document.getElementById("x").dispatchEvent(ev) + </script> + </body> +</html>The
debugfunction will be invoked twice. Each time the event’stargetattribute value will be thespanelement. The first timecurrentTargetattribute’s @@ -486,7 +486,7 @@
AT_TARGET. 3.2. Interface
Event[Constructor(DOMString type, optional EventInit eventInitDict), - Exposed=(Window,Worker)] + Exposed=(Window,Worker)] interface Event { readonly attribute DOMString type; readonly attribute EventTarget? target; @@ -508,7 +508,7 @@readonly attribute boolean defaultPrevented; readonly attribute boolean composed; - [Unforgeable] readonly attribute boolean isTrusted; + [Unforgeable] readonly attribute boolean isTrusted; readonly attribute DOMTimeStamp timeStamp; void initEvent(DOMString type, boolean bubbles, boolean cancelable); // historical @@ -592,7 +592,14 @@
context object’s path:
4.2.10.2. Interface HTMLCollection
-[Exposed=Window, LegacyUnenumerableNamedProperties] +[Exposed=Window, LegacyUnenumerableNamedProperties] interface HTMLCollection { readonly attribute unsigned long length; getter Element? item(unsigned long index); @@ -2014,12 +2021,12 @@<