[whatwg] navigation shouldn't abort if canceled
mikewse at hotmail.com
Sun Jun 19 08:52:34 PDT 2011
Ian Hickson wrote:
> On Sun, 26 Dec 2010, Mike Wilson wrote:
> > (as of December 26, 2010)
> > | When a browsing context is navigated to a new resource, the
> > | user agent must run the following steps:
> > ...
> > | 9. Abort the active document of the browsing context.
> > ...
> > | 11. Prompt to unload the Document object. If the user refused
> > | to allow the document to be unloaded, then these steps
> > | must be aborted.
> > Might this be a bug? (It seems more consistent with other
> parts of the
> > html5 spec, and with browsers, to do the abort after the user has
> > allowed the document to unload.)
> These tests suggest that it's what WebKit does but isn't what Firefox
> does. I tried testing Opera and IE but other bugs prevented me from
> getting conclusive results from them.
FWIW, I tried the following tags in a bunch of browsers (including
IE, Chrome and Safari):
and none of them were aborted on a dismissed (beforeunload prompted)
> On Tue, 1 Feb 2011, Mike Wilson wrote:
> > Consequences of the current text are that resource fetches
> are canceled
> > for a document when navigating away from it, even if the user then
> > chooses to cancel the navigation at a "beforeunload" prompt
> and returns
> > to the document.
> Fair point. Fixed. The spec now matches Firefox on this.
Thanks Ian, that looks much better now.
More information about the whatwg