[whatwg] readyState transitions when aborting a document

Henri Sivonen hsivonen at iki.fi
Thu Apr 19 04:43:12 PDT 2012

I've been trying to make document.readyState transitions less broken
in Gecko. (The transitions are very sad as of Firefox 13 in pretty
much all but the most trivial cases.)

I'm having a particularly hard time figuring out what the right thing
to do is when it comes to aborting document loads. Unfortunately, I
don't trust the spec to describe the Web-compatible truth.
 * Is there a way to abort a document load in IE without causing
immediate navigation away from the document? IE doesn't support
 * 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
 * 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?
 * Should window.stop() really not abort the parser like the spec
seems to suggest?
 * Should reaching "complete" always involve firing "load"?
 * Should reaching "interactive" always involve firing "DOMContentLoaded"?
 * Does anyone have test cases for this stuff?

Henri Sivonen
hsivonen at iki.fi

More information about the whatwg mailing list