Boris Zbarsky wrote: > > As I wrote in my initial post, my observation was actually > > that this is contrary to current browser behaviour. > > Ah, I see. > > So in Gecko, at least, beforeunload fires before the document > is aborted.
Right, that matches my findings in other browsers as well. So can we then say that http://www.whatwg.org/specs/web-apps/current-work/#navigating-across-documen ts probably needs updating? Is the fix as simple as moving step 9 to the position between current step 11 and 12? (directly after beforeunload) Best regards Mike
