Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    primarykey
    data
    text
    <p>This was not, so far as i know, explicitly defined in the past. Different browsers are free to implement event ordering however they see fit. While most are close enough for all practical purposes, there have been and continue to be some odd edge cases where browsers differ somewhat (and, of course, the many more cases where certain browsers fail to send certain events <em>at all</em>).</p> <p>That said, the <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html" rel="noreferrer">HTML 5 draft recommendation</a> does make an attempt to specify how events will be queued and dispatched - <a href="http://www.whatwg.org/specs/web-apps/current-work/multipage/browsers.html#event-loops" rel="noreferrer">the event loop</a>:</p> <blockquote> <p>To coordinate events, user interaction, scripts, rendering, networking, and so forth, user agents must use event loops as described in this section.</p> <p>There must be at least one event loop per user agent, and at most one event loop per unit of related similar-origin browsing contexts.</p> <p>An event loop has one or more task queues. A task queue is an ordered list of tasks [...] When a user agent is to queue a task, it must add the given task to one of the task queues of the relevant event loop. All the tasks from one particular task source must always be added to the same task queue, but tasks from different task sources may be placed in different task queues. [...]</p> <p>[...]a user agent could have one task queue for mouse and key events (the user interaction task source), and another for everything else. The user agent could then give keyboard and mouse events preference over other tasks three quarters of the time, keeping the interface responsive but not starving other task queues, and never processing events from any one task source out of order. [...]</p> </blockquote> <p>Note that last bit: it is up to the browser implementation to determine which events will be grouped together and processed in order, as well as the priority given to any particular type of event. Therefore, there's little reason to expect all browsers to dispatch <em>all</em> events in a fixed order, now or in the future.</p>
    singulars
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    plurals
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. This table or related slice is empty.
    1. VO
      singulars
      1. This table or related slice is empty.
    2. VO
      singulars
      1. This table or related slice is empty.
    3. VO
      singulars
      1. This table or related slice is empty.
    1. This table or related slice is empty.
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload