From 622dd40605cfc8db3f76951b946bddfb4253dde8 Mon Sep 17 00:00:00 2001 From: Dominic Farolino Date: Fri, 20 Dec 2024 17:22:35 -0500 Subject: [PATCH] Wrapping and formatting nits --- source | 22 ++++++++++------------ 1 file changed, 10 insertions(+), 12 deletions(-) diff --git a/source b/source index fd958976466..e4218a49149 100644 --- a/source +++ b/source @@ -29485,8 +29485,8 @@ interface HTMLImageElement : HTMLElement { oldParent, are:

    -

  1. If oldParent is a picture element, then, count this as a - relevant mutation for movedNode.

    2. +

  2. If oldParent is a picture element, then, count this as a relevant mutation for movedNode.

The img HTML element removing steps, given removedNode and @@ -36605,9 +36605,7 @@ interface MediaError { pointer must be updated as follows:

-
If a new node is inserted or moved between the two nodes that define - pointer
+
If a new node is inserted or moved between the two nodes that define pointer
Let pointer be the point between the node before pointer and the new node. In other words, insertions at pointer go after pointer.
@@ -72452,8 +72450,8 @@ document.body.append(parent); elements as well. By default, the "disconnectedCallback" and "connectedCallback" would be called on the element, one after the other. This is done to maintain compatibility with existing custom elements that predate the moveBefore() method. This means that by default, custom elements - reset their state as if they were removed and re-inserted. In the example moveBefore() method. This means that by default, custom + elements reset their state as if they were removed and re-inserted. In the example above, the impact would be that the observer would be disconnected and re-connected, and the tab index would be reset.

@@ -72461,10 +72459,10 @@ document.body.append(parent); data-x="concept-node-move-ext">moving, the author can implement a "connectedMoveCallback". The existence of this callback, even if empty, would supercede the default behavior of calling "disconnectedCallback" and "connectedCallback". "connectedMoveCallback" can also be - an appropriate place to execute logic that depends on the element's ancestors. For example:

+ data-x="">connectedCallback". "connectedMoveCallback" can also be an + appropriate place to execute logic that depends on the element's ancestors. For example:

- 
class TacoButton extends HTMLElement {
+  
class TacoButton extends HTMLElement {
   static observedAttributes = ["disabled"];
 
   constructor() {
@@ -72714,8 +72712,8 @@ document.body.append(parent);
    
A collection of lifecycle callbacks

    
A map, whose keys are the strings "connectedCallback",
-   "disconnectedCallback", "adoptedCallback",
-   "connectedMoveCallback",
+   "disconnectedCallback", "adoptedCallback", "connectedMoveCallback",
    "attributeChangedCallback",
    "formAssociatedCallback",
    "formDisabledCallback",