Fire events at least for async removal

Author: domenic

source

@@ -1813,7 +1813,8 @@ a.setAttribute('href', 'https://example.com/'); // change the content attribute
 
     <p class="note">This does <em>not</em> perform the <span>unfocusing steps</span>,
     <span>focusing steps</span>, or <span>focus update steps</span>, and thus no <code
-    data-x="event-blur">blur</code> event is fired.</p>
+    data-x="event-blur">blur</code> or <code data-x="event-change">change</code> events are
+    fired.</p>
    </li>
 
    <li><p>If <var>removedNode</var> is an element whose <span
@@ -77073,8 +77074,9 @@ partial interface <span id="NavigatorUserActivation-partial">Navigator</span> {
       named <code data-x="event-blur">blur</code> at <var>blur event target</var>, with
       <var>related blur target</var> as the related target.</p>
 
-      <p class="note">In some cases, e.g. if <var>entry</var> is an <code>area</code>
-      element's shape, a scrollable region, or a <span>viewport</span>, no event is fired.</p>
+      <p class="note" id="note-sometimes-no-blur-event">In some cases, e.g. if <var>entry</var> is
+      an <code>area</code> element's shape, a scrollable region, or a <span>viewport</span>, no
+      event is fired.</p>
      </li>
     </ol>
    </li>
@@ -96730,21 +96732,22 @@ import "https://example.com/foo/../module2.mjs";</code></pre>
      <li id="focus-fixup-rule">
       <p>For each <span>fully active</span> <code>Document</code> in <var>docs</var>, if the <span
       data-x="focused area of the document">focused area</span> of that <code>Document</code> is no
-      longer a <span>focusable area</span>, then set that <code>Document</code>'s <span
-      data-x="focused area of the document">focused area</span> to its <span>viewport</span>.</p>
+      longer a <span>focusable area</span>, then run the <span>focusing steps</span> for that
+      <code>Document</code>'s <span>viewport</span>.</p>
 
       <p class="example">For example, this might happen because an element has the <code
       data-x="attr-hidden">hidden</code> attribute added, causing it to stop <span>being
       rendered</span>. It might also happen to an <code>input</code> element when the element gets
       <span data-x="concept-fe-disabled">disabled</span>.</p>
 
-      <p class="note">This does <em>not</em> perform the <span>unfocusing steps</span>,
-      <span>focusing steps</span>, or <span>focus update steps</span>, and thus no <code
-      data-x="event-blur">blur</code> event is fired.</p>
+      <p class="note">This will <a href="#note-sometimes-no-blur-event">usually</a> fire <code
+      data-x="event-blur">blur</code> events, and possibly <code data-x="event-change">change</code>
+      events.</p>
 
       <p class="note">In addition to this asynchronous fixup, if the <span>focused area of the
       document</span> is removed, there is a <a href="#node-remove-focus-fixup">synchronous
-      fixup</a>.</p>
+      fixup</a>. That one will <em>not</em> fire <code data-x="event-blur">blur</code> or <code
+      data-x="event-change">change</code> events.</p>
      </li>
 
      <li>