[whatwg] Readiness of script-created documents
jonas at sicking.cc
Wed Apr 25 10:57:46 PDT 2012
On Mon, Apr 23, 2012 at 4:55 AM, Henri Sivonen <hsivonen at iki.fi> wrote:
> On Mon, Jun 20, 2011 at 3:10 PM, Jonas Sicking <jonas at sicking.cc> wrote:
>> On Mon, Jun 20, 2011 at 4:26 AM, Henri Sivonen <hsivonen at iki.fi> wrote:
>>> It says "complete" in Firefox, "loading" in Chrome and Opera and
>>> "uninitialized" in IE. The spec requires "complete". readyState is
>>> originally an IE API. Why doesn't the spec require "uninitialized"?
>>> (The implementation in Gecko is so recent that it's quite possible that
>>> Gecko followed the spec and the spec just made stuff up as opposed to
>>> the spec following Gecko.)
>> "complete" seems like the most useful and consistent value which would
>> seem like a good reason to require that.
> Why don't aborted documents reach "complete" in Gecko? It seems weird
> to have aborted documents stay in the "loading" state when they are
> not, in fact, loading.
Sounds like a bug, I don't think this was done on purpose. I agree
that we should ideally only be in "loading" when we're actually
More information about the whatwg