AFAIK, only one event can run at a time. JavaScript has only one thread, so an event generated while another event listener is executing is placed in a queue, to be executed when the current execution thread is done. With onunload, the entire page is unloaded after the event (if it returns true), so the next event in the queue is ignored.
Marius Gundersen On Tue, Sep 22, 2009 at 3:45 PM, Adam Barth <wha...@adambarth.com> wrote: > I looked around in the HTML5 draft, but it wasn't obvious to me if it > explains how to handle navigation events generated during the unload > event. As far as I can tell by testing browsers, these navigation > events are ignored. > > Adam >
