Update all "queue a task" invocations to explicitly specify their task source

[domenic]

The spec currently is not very precise about how you specify the task source when queuing the task. Lots of parts of the spec do so via nearby sentences such as

The task source for the tasks mentioned above is the DOM manipulation task source

or

The task source for the tasks queued by algorithms in this section is the DOM manipulation task source.

or even

Queue a task to run the iframe load event steps.

The task source for this task is the DOM manipulation task source.

The way in which you have to search around to find the actual task source is frustrating and has led to some confusion in the past. (TODO citation needed.)

#4465 proposes that we explicitly use "Queue a task on the X task source to ..." from now on. This issue tracks updating the rest of the spec to do so, once that lands.

---

I am tagging this as "good first issue", and help would be appreciated working through it. Once #4465 lands, the work here should consist of:

• Finding all instances of "queue a task" in the spec. This can be done by going to https://html.spec.whatwg.org/#queue-a-task and clicking on the <dfn> to see a popup listing everywhere that uses it.
• Updating all of them to be of the form "queue a task on the X task source". To figure out X, search nearby for statements like the ones I listed above. (Some may already be of this form.)
• Delete those now-redundant statements.

If someone wants to work on this, I suggest they first try it on one or two sections, then send a pull request, and we can make sure the process works out. Then you can unleash yourself on the rest of the spec :).

[gterzian]

The way in which you have to search around to find the actual task source is frustrating and has led to some confusion in the past. (TODO citation needed.)

A citation from a personal experience:

1. The whatwg/html/ issue: When to "fail the connection" of an EventSource? #3789
2. The implementation side: Aborting a document shoud only cancel tasks from the networking task source servo/servo#21114

[domenic]

Note that #4465 has landed, so if anyone wants to take on this issue, the groundwork is ready :)

[littledan]

Do you have a recommendation for how to define infrequently used or single-use task sources? In PRs I am working on, I am using the new "on the..." wording, but maintain those redundant statements to define the task source in the section. See #4613 (comment) and #4571.

Should I put a <dfn> around the first usage? Or define all these infrequently used task sources with the frequently used others above? Something else?

Edit: @TimothyGu pointed out that there are multiple precedents to the inline dfn wording, so I will go with that.