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

[whatwg] Readiness of script-created documents

From: Henri Sivonen <hsivonen@iki.fi>
Date: Mon, 23 Apr 2012 14:55:48 +0300
Message-ID: <CAJQvAueHBBBUFHgsWC0iC7=CHSnq4WyuKFA_b=MsT6HhrCBxcg@mail.gmail.com>
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:
>> http://software.hixie.ch/utilities/js/live-dom-viewer/saved/1039
>> 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.

Henri Sivonen
hsivonen at iki.fi
Received on Monday, 23 April 2012 04:55:48 UTC

This archive was generated by hypermail 2.4.0 : Wednesday, 22 January 2020 16:59:41 UTC