W3C home > Mailing lists > Public > whatwg@whatwg.org > August 2008

[whatwg] document.readyState and its initial value

From: Jonas Sicking <jonas@sicking.cc>
Date: Tue, 05 Aug 2008 15:49:59 -0700
Message-ID: <4898D917.2020208@sicking.cc>
Ian Hickson wrote:
> On Tue, 5 Aug 2008, Jonas Sicking wrote:
>> Ian Hickson wrote:
>>>> But, oddity is par for the course in DOM, so I guess we'll just follow the
>>>> HTML 5 spec as-is, initialize readyState to "loading" in the object
>>>> constructor, and keep our fingers crossed.
>>> If you find any problems with doing this, please let me know, so we can
>>> update the spec!
>> The concern I have with doing that is that document created through 
>> other means, such as .implementation.createDocument, 
>> XSLTProccessor.transformToDocument, DOMParser.parse, etc, probably 
>> should not be in the 'uninitialized' state. Especially the last two 
>> should return documents that is in the 'complete' state I would think.
> 
> IE doesn't have any of those mechanisms. In IE,
> 
>    w(new ActiveXObject("Msxml.DOMDocument").readyState);
> 
> ...returns "4", which isn't any of the values I expected.
> 
> Right now the spec says that anything that doesn't go through a parser 
> will remain in the readyState == "loading" state forever. Is that a 
> problem?

The one usecase I have heard for .readystate is to figure out if the 
document has had its onload event fired yet, or if one is coming later. 
In that scenario it would seem unexpected to return "loading" as no 
onload event is about to fire.

> We could define that mechanisms that create a Document object 
> without an associated parser set it to "complete" if you want. I'm not 
> sure that that would be especially useful, although it would, I guess, be 
> somewhat more self-consistent.

Yeah, i think so.

/ Jonas
Received on Tuesday, 5 August 2008 15:49:59 UTC

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