如何理解规范事件循环中任务队列未派发的事件？
How to understand the event which not dispatched by task queue in event loop of spec?
在spec中：
Not all events are dispatched using the task queue, many are dispatched during other tasks.
我想知道上面的"many"和"other tasks"指的是什么？
如果您在 HTML 规范中搜索短语 “触发事件”，您会看到它显示 “排队任务”的案例触发一个事件” 并放置它只是说 “触发一个事件” 而没有 “排队任务”。 For example:
Each document has a current document readiness. … When the value is set, the user agent must fire an event named readystatechange at the Document object.
将上面的语言与 the following spec excerpt 中的语言进行比较：
… the user agent must, if the loads were successful, queue a task to fire an event named load at the link element…
因此，当规范不是说“排队任务以触发事件”而是说“触发事件”时，事件不会进入任务队列，而是必须同步触发。
在spec中：
Not all events are dispatched using the task queue, many are dispatched during other tasks.
我想知道上面的"many"和"other tasks"指的是什么？
如果您在 HTML 规范中搜索短语 “触发事件”，您会看到它显示 “排队任务”的案例触发一个事件” 并放置它只是说 “触发一个事件” 而没有 “排队任务”。 For example:
Each document has a current document readiness. … When the value is set, the user agent must fire an event named
readystatechangeat theDocumentobject.
将上面的语言与 the following spec excerpt 中的语言进行比较：
… the user agent must, if the loads were successful, queue a task to fire an event named
loadat thelinkelement…
因此，当规范不是说“排队任务以触发事件”而是说“触发事件”时，事件不会进入任务队列，而是必须同步触发。