Convert more "queue a task" to "queue an element task"

This accounts for <embed>, <frame>, <img>, <object>, form controls, and
a couple other spot-fixes.

Part of #4980.

Author: dtapuska

source

@@ -24288,10 +24288,10 @@ document.body.appendChild(wbr);</code></pre>
    it is in no state.</p></li>
 
    <li><p>If <var>destination</var> is not <span
-   data-x="concept-script-like-destination">script-like</span>, then <span>queue a task</span> on
-   the <span>networking task source</span> to <span data-x="concept-event-fire">fire an event</span>
-   named <code data-x="event-error">error</code> at the <code>link</code> element, and
-   return.</p></li>
+   data-x="concept-script-like-destination">script-like</span>, then <span>queue an element
+   task</span> on the <span>networking task source</span> given the <code>link</code> element to
+   <span data-x="concept-event-fire">fire an event</span> named <code
+   data-x="event-error">error</code> at the <code>link</code> element, and return.</p></li>
 
    <li><p><span data-x="parse a url">Parse</span> the <span>URL</span> given by the <code
    data-x="attr-link-href">href</code> attribute, relative to the element's <span>node
@@ -27180,10 +27180,6 @@ was an English &lt;a href="/wiki/Music_hall">music hall&lt;/a> singer, ...</code
 
   <h5 id="images-processing-model">Processing model</h5>
 
-  <p>The <span>task source</span> for the <span data-x="concept-task">tasks</span> <span
-  data-x="queue a task">queued</span> by algorithms in this section is the <span>DOM manipulation
-  task source</span>.</p>
-
   <hr>
 
   <p>An <code>img</code> element has a <dfn>current request</dfn> and a <dfn>pending request</dfn>.
@@ -27677,9 +27673,9 @@ was an English &lt;a href="/wiki/Music_hall">music hall&lt;/a> singer, ...</code
    <li><p>If <var>urlString</var> is the same as the <span>current request</span>'s <span
    data-x="img-req-url">current URL</span> and <span>current request</span>'s <span
    data-x="img-req-state">state</span> is <span data-x="img-inc">partially available</span>, then
-   <span>abort the image request</span> for the <span>pending request</span>, <span>queue a
-   task</span> to <span>restart the animation</span> if <i>restart animation</i> is set, and
-   return.</p></li>
+   <span>abort the image request</span> for the <span>pending request</span>, <span>queue an element
+   task</span> on the <span>DOM manipulation task source</span> given the <code>img</code> element
+   to <span>restart the animation</span> if <i>restart animation</i> is set, and return.</p></li>
 
    <li><p>If the <span>pending request</span> is not null, then <span>abort the image request</span>
    for the <span>pending request</span>.</p></li>
@@ -27724,7 +27720,8 @@ was an English &lt;a href="/wiki/Music_hall">music hall&lt;/a> singer, ...</code
      <li><p>Wait until the <span>will lazy load image steps</span> no longer return true, given the
      <code>img</code>.</p></li>
 
-     <li><p><span>Queue a task</span> to continue running the rest of this algorithm.</p></li>
+     <li><p><span>Queue an element task</span> on the <span>DOM manipulation task source</span>
+     given the <code>img</code> element to continue running the rest of this algorithm.</p></li>
     </ol>
    </li>
 
@@ -27807,8 +27804,9 @@ was an English &lt;a href="/wiki/Music_hall">music hall&lt;/a> singer, ...</code
       replace the previous image. Once one body part has been completely decoded, the user agent
       must set the <code>img</code> element's <span>current request</span>'s <span
       data-x="img-req-state">state</span> to <span data-x="img-all">completely available</span> and
-      <span>queue a task</span> to <span data-x="concept-event-fire">fire an event</span> named
-      <code data-x="event-load">load</code> at the <code>img</code> element.</p>
+      <span>queue an element task</span> on the <span>DOM manipulation task source</span> given the
+      <code>img</code> element to <span data-x="concept-event-fire">fire an event</span> named <code
+      data-x="event-load">load</code> at the <code>img</code> element.</p>
       <!--TODO what if the image is broken?
           TODO change state and fire in the same task? -->
      </dd>
@@ -27891,7 +27889,8 @@ was an English &lt;a href="/wiki/Music_hall">music hall&lt;/a> singer, ...</code
      data-x="img-error">broken</span>, <span>abort the image request</span> for the <span>current
      request</span> and the <span>pending request</span>, <span>upgrade the pending request to the
      current request</span> if <var>image request</var> is the <span>pending request</span>, and
-     then <span>queue a task</span> to <span data-x="concept-event-fire">fire an event</span> named
+     then <span>queue an element task</span> on the <span>DOM manipulation task source</span> given
+     the <code>img</code> element to <span data-x="concept-event-fire">fire an event</span> named
      <code data-x="event-error">error</code> at the <code>img</code> element.</p></dd>
     </dl>
    </li>
@@ -30319,8 +30318,8 @@ interface <dfn>HTMLEmbedElement</dfn> : <span>HTMLElement</span> {
   remaining <span data-x="concept-embed-active">potentially active</span> and has its <code
   data-x="attr-embed-type">src</code> attribute set, changed, or removed or its <code
   data-x="attr-embed-type">type</code> attribute set, changed, or removed, the user agent must
-  <span>queue a task</span> using the <dfn>embed task source</dfn> to run <span>the
-  <code>embed</code> element setup steps</span> for that element.</p>
+  <span>queue an element task</span> on the <dfn>embed task source</dfn> given the element
+  to run <span>the <code>embed</code> element setup steps</span> for that element.</p>
 
   <p><dfn>The <code>embed</code> element setup steps</dfn> for a given <code>embed</code> element
   <var>element</var> are as follows:</p>
@@ -30404,7 +30403,8 @@ interface <dfn>HTMLEmbedElement</dfn> : <span>HTMLElement</span> {
            context</span>.</p></li>
 
            <li><p>When the <code>Document</code> of <var>element</var>'s <span>nested browsing
-           context</span> is marked as <span>completely loaded</span>, <span>queue a task</span> to
+           context</span> is marked as <span>completely loaded</span>, <span>queue an element
+           task</span> on the <span>DOM manipulation task source</span> given <var>element</var> to
            <span data-x="concept-event-fire">fire an event</span> named <code
            data-x="event-load">load</code> at <var>element</var>.</p></li>
           </ol>
@@ -30496,8 +30496,9 @@ interface <dfn>HTMLEmbedElement</dfn> : <span>HTMLElement</span> {
 
    <li><p><var>element</var> now <span>represents</span> this <span>plugin</span> instance.</p></li>
 
-   <li><p>Once the plugin, and <var>response</var> if given, are completely loaded, <span>queue a
-   task</span> to <span data-x="concept-event-fire">fire an event</span> named <code
+   <li><p>Once the plugin, and <var>response</var> if given, are completely loaded, <span>queue an
+   element task</span> on the <span>DOM manipulation task source</span> give <var>element</var> to
+   <span data-x="concept-event-fire">fire an event</span> named <code
    data-x="event-load">load</code> at <var>element</var>.</p></li>
   </ol>
 
@@ -30545,9 +30546,6 @@ interface <dfn>HTMLEmbedElement</dfn> : <span>HTMLElement</span> {
 
   <p>The <code>embed</code> element <span>potentially delays the load event</span>.</p>
 
-  <p>The <span>task source</span> for the <span data-x="concept-task">tasks</span> mentioned in this
-  section is the <span>DOM manipulation task source</span>.</p>
-
   </div>
 
   <p>Any namespace-less attribute other than <code data-x="attr-embed-name">name</code>, <code
@@ -30731,13 +30729,14 @@ interface <dfn>HTMLObjectElement</dfn> : <span>HTMLElement</span> {
 
   </ul> <!-- Changing the base URL doesn't trigger this. -->
 
-  <p>...the user agent must <span>queue a task</span> to run the following steps to (re)determine
+  <p>...the user agent must <span>queue an element task</span> on the <span>DOM manipulation task
+  source</span> given the <code>object</code> element to run the following steps to (re)determine
   what the <code>object</code> element represents. This <span data-x="concept-task">task</span>
   being <span data-x="queue a task">queued</span> or actively running must <span>delay the load
-  event</span> of the element's <span>node document</span>. <!--As described in the algorithm, once the algorithm
-  starts fetching a resource, the fetch is what starts delaying the load event. But to tide us over
-  from when the parser finds the <object> element and the fetching begins, we have to block the load
-  event like this, lest the parse end before this task gets run.--></p>
+  event</span> of the element's <span>node document</span>. <!--As described in the algorithm, once
+  the algorithm starts fetching a resource, the fetch is what starts delaying the load event. But to
+  tide us over from when the parser finds the <object> element and the fetching begins, we have to
+  block the load event like this, lest the parse end before this task gets run.--></p>
 
   <ol>
    <li>
@@ -31087,7 +31086,8 @@ interface <dfn>HTMLObjectElement</dfn> : <span>HTMLElement</span> {
         gets further navigated to other locations.)</p>
 
         <p>If the <span>URL</span> of the given resource <em>is</em> <code>about:blank</code>, then,
-        instead, the user agent must <span>queue a task</span> to <span
+        instead, the user agent must <span>queue an element task</span> on the <span>DOM
+        manipulation task source</span> given the <code>object</code> element to <span
         data-x="concept-event-fire">fire an event</span> named <code data-x="event-load">load</code>
         at the <code>object</code> element. <span class="note">No <code
         data-x="event-load">load</code> event is fired at the <code>about:blank</code> document
@@ -31144,9 +31144,10 @@ interface <dfn>HTMLObjectElement</dfn> : <span>HTMLElement</span> {
      represents.</p>
 
      <li>
-      <p>Return. Once the resource is completely loaded, <span>queue a task</span> to
-      <span data-x="concept-event-fire">fire an event</span> named <code
-      data-x="event-load">load</code> at the element.</p>
+      <p>Return. Once the resource is completely loaded, <span>queue an element task</span> on the
+      <span>DOM manipulation task source</span> given the <code>object</code> element to <span
+      data-x="concept-event-fire">fire an event</span> named <code data-x="event-load">load</code>
+      at the element.</p>
      </li>
     </ol>
    </li>
@@ -31159,7 +31160,8 @@ interface <dfn>HTMLObjectElement</dfn> : <span>HTMLElement</span> {
    <span data-x="concept-plugin-secure">secured</span>, then that <span>plugin</span> <a
    href="#object-plugin">should be used</a>. If these conditions cannot be met, or if the
    <span>plugin</span> reports an error, jump to the step below labeled <i>fallback</i>. Otherwise
-   return; once the plugin is completely loaded, <span>queue a task</span> to <span
+   return; once the plugin is completely loaded, <span>queue an element task</span> on the
+   <span>DOM manipulation task source</span> given the <code>object</code> element to <span
    data-x="concept-event-fire">fire an event</span> named <code data-x="event-load">load</code> at
    the element.</p></li>
 
@@ -31194,9 +31196,6 @@ interface <dfn>HTMLObjectElement</dfn> : <span>HTMLElement</span> {
 
   <p>The <code>object</code> element <span>potentially delays the load event</span>.</p>
 
-  <p>The <span>task source</span> for the <span data-x="concept-task">tasks</span> mentioned in this
-  section is the <span>DOM manipulation task source</span>.</p>
-
   </div>
 
   <p>The <code data-x="attr-hyperlink-usemap">usemap</code> attribute, if present while the
@@ -31637,7 +31636,8 @@ interface <dfn>HTMLVideoElement</dfn> : <span>HTMLMediaElement</span> {
   (including, for example, because the <span data-x="dom-VideoTrack-selected">selected video
   track</span> was changed), if the element's <code data-x="dom-media-readyState">readyState</code>
   attribute is not <code data-x="dom-media-HAVE_NOTHING">HAVE_NOTHING</code>, the user agent must
-  <span>queue a task</span> to <span data-x="concept-event-fire">fire an event</span> named <code
+  <span>queue an element task</span> on the <span>media element event task source</span> given the
+  <span>media element</span> to <span data-x="concept-event-fire">fire an event</span> named <code
   data-x="event-media-resize">resize</code> at the <span>media element</span>.</p>
 
   </div>
@@ -49413,7 +49413,8 @@ interface <dfn>HTMLSelectElement</dfn> : <span>HTMLElement</span> {
   user agent must <span>send <code>select</code> update notifications</span>.</p>
 
   <p>When the user agent is to <dfn>send <code>select</code> update notifications</dfn>, <span>queue
-  a task</span>, using the <span>user interaction task source</span>, to run these steps:</p>
+  an element task</span> on the <span>user interaction task source</span> given the <code>select</code>
+  element to run these steps:</p>
 
   <ol>
    <li><p><span data-x="concept-event-fire">Fire an event</span> named <code
@@ -50309,12 +50310,13 @@ interface <dfn>HTMLTextAreaElement</dfn> : <span>HTMLElement</span> {
   data-x="attr-textarea-readonly">readonly</code> attribute specified.</p>
 
   <p>When a <code>textarea</code> is <span data-x="concept-fe-mutable">mutable</span>, its <span
-  data-x="concept-textarea-raw-value">raw value</span> should be editable by the user: the user agent
-  should allow the user to edit, insert, and remove text, and to insert and remove line breaks in
-  the form of U+000A LINE FEED (LF) characters. Any time the user causes the element's <span
-  data-x="concept-textarea-raw-value">raw value</span> to change, the user agent must <span>queue a
-  task</span> to <span data-x="concept-event-fire">fire an event</span> named <code
-  data-x="event-input">input</code> at the <code>textarea</code> element, with the <code
+  data-x="concept-textarea-raw-value">raw value</span> should be editable by the user: the user
+  agent should allow the user to edit, insert, and remove text, and to insert and remove line breaks
+  in the form of U+000A LINE FEED (LF) characters. Any time the user causes the element's <span
+  data-x="concept-textarea-raw-value">raw value</span> to change, the user agent must <span>queue an
+  element task</span> on the <span>user interaction task source</span> given the
+  <code>textarea</code> element to <span data-x="concept-event-fire">fire an event</span> named
+  <code data-x="event-input">input</code> at the <code>textarea</code> element, with the <code
   data-x="dom-Event-bubbles">bubbles</code> attribute initialized to true. User agents may wait for
   a suitable break in the user's interaction before queuing the task; for example, a user agent
   could wait for the user to have not hit a key for 100ms, so as to only fire the event when the
@@ -54245,8 +54247,8 @@ MIT Room 32-G524
 
    <li><p>If the previous steps caused the <span
    data-x="concept-textarea/input-selection">selection</span> of the text control to be modified (in
-   either extent or <span data-x="selection direction">direction</span>), then <span>queue a
-   task</span>, using the <span>user interaction task source</span>, to <span
+   either extent or <span data-x="selection direction">direction</span>), then <span>queue an
+   element task</span> on the <span>user interaction task source</span> given the element to <span
    data-x="concept-event-fire">fire an event</span> named <code data-x="event-select">select</code>
    at the element, with the <code data-x="dom-Event-bubbles">bubbles</code> attribute initialized to
    true.</p></li>
@@ -112497,10 +112499,11 @@ details[open] > summary {
   <span>'inline-block'</span> box depicting a text control that obscures data entry.</p>
 
   <p>If these text controls provide a text selection, then, when the user changes the current
-  selection, the user agent is expected to <span>queue a task</span>, using the <span>user
-  interaction task source</span>, to <span data-x="concept-event-fire">fire an event</span> named
-  <code data-x="event-select">select</code> at the element, with the <code
-  data-x="dom-Event-bubbles">bubbles</code> attribute initialized to true.</p>
+  selection, the user agent is expected to <span>queue an element task</span> on the <span>user
+  interaction task source</span> given the <code>input</code> element to <span
+  data-x="concept-event-fire">fire an event</span> named <code data-x="event-select">select</code>
+  at the element, with the <code data-x="dom-Event-bubbles">bubbles</code> attribute initialized to
+  true.</p>
 
   <p>If an <code>input</code> element whose <code data-x="attr-input-type">type</code> attribute is
   in one of the above states has a <code data-x="attr-input-size">size</code> attribute, and parsing
@@ -112931,11 +112934,11 @@ marquee {
 
   <p>The <code>textarea</code> element is expected to render as an <span>'inline-block'</span> box
   depicting a multiline text control. If this multiline text control provides a selection, then,
-  when the user changes the current selection, the user agent is expected to <span>queue a
-  task</span>, using the <span>user interaction task source</span>, to <span
-  data-x="concept-event-fire">fire an event</span> named <code data-x="event-select">select</code>
-  at the element, with the <code data-x="dom-Event-bubbles">bubbles</code> attribute initialized to
-  true.</p>
+  when the user changes the current selection, the user agent is expected to <span>queue an element
+  task</span> on the <span>user interaction task source</span> given the <code>textarea</code>
+  element to <span data-x="concept-event-fire">fire an event</span> named <code
+  data-x="event-select">select</code> at the element, with the <code
+  data-x="dom-Event-bubbles">bubbles</code> attribute initialized to true.</p>
 
   <p>If the element has a <code data-x="attr-textarea-cols">cols</code> attribute, and parsing that
   attribute's value using the <span>rules for parsing non-negative integers</span> doesn't generate
@@ -114236,9 +114239,9 @@ interface <dfn>HTMLFrameSetElement</dfn> : <span>HTMLElement</span> {
    <dt>If the element has no <code undefined data-x="attr-frame-src">src</code> attribute specified,
    and the user agent is processing the <code>frame</code>'s attributes for the first time</dt>
 
-   <dd><p><span>Queue a task</span> to <span data-x="concept-event-fire">fire an event</span> named
-   <code data-x="event-load">load</code> at the <code>frame</code> element using the <span>DOM
-   manipulation task source</span>.</p></dd>
+   <dd><p><span>Queue an element task</span> on the <span>DOM manipulation task source</span> given
+   the <code>frame</code> element to <span data-x="concept-event-fire">fire an event</span> named
+   <code data-x="event-load">load</code> at the <code>frame</code> element.</p></dd>
 
    <dt>Otherwise</dt>