W3C home > Mailing lists > Public > whatwg@whatwg.org > April 2012

[whatwg] readyState transitions when aborting a document

From: Henri Sivonen <hsivonen@iki.fi>
Date: Fri, 20 Apr 2012 16:54:07 +0300
Message-ID: <CAJQvAuetpDUDa+XMNuxObv34tk3=7fLDS_s=T19QgHpDbh6DaQ@mail.gmail.com>
On Thu, Apr 19, 2012 at 2:43 PM, Henri Sivonen <hsivonen at iki.fi> wrote:
> ?* Is there a way to abort a document load in IE without causing
> immediate navigation away from the document? IE doesn't support
> window.stop().

Yes. document.execCommand("Stop")

> ?* Does Web compatibility ever require a transition from "loading" to
> "complete" without an intermediate "interactive" state? ?(Both chrome
> and Firefox as shipped make such transitions, but those might be
> bugs.)

I have no evidence to say anything sure here, but I doubt Web compat
requires transitions from "loading" to "complete". What actually
happens varies a lot.

> ?* Should the aborted documents stay in the "loading" state forever
> like the spec says or should they reach the "complete" state
> eventually when the event loop spins?

Gecko and WebKit disagree.

> ?* Should window.stop() really not abort the parser like the spec
> seems to suggest?

Looks like Opera is alone with the non-aborting behavior. The spec is wrong.

> ?* Should reaching "complete" always involve firing "load"?

Not in WebKit.

> ?* Should reaching "interactive" always involve firing "DOMContentLoaded"?

Probably.

> ?* Does anyone have test cases for this stuff?

Demos: http://hsivonen.iki.fi/test/moz/readystate/

-- 
Henri Sivonen
hsivonen at iki.fi
http://hsivonen.iki.fi/
Received on Friday, 20 April 2012 06:54:07 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Wednesday, 30 January 2013 18:48:07 GMT