W3C home > Mailing lists > Public > public-webapi@w3.org > April 2006

ISSUE-66: should Documents that aren\'t being presented be required to have a null defaultView?

From: Web APIs Issue Tracker <dean+cgi@w3.org>
Date: Tue, 4 Apr 2006 09:23:13 +0000 (GMT)
To: public-webapi@w3.org
Message-Id: <20060404092313.9DC8466367@dolph.w3.org>


ISSUE-66: should Documents that aren't being presented be required to have a null defaultView?

http://www.w3.org/2005/06/tracker/webapi/issues/66

Raised by: Maciej Stachowiak
On product: Window

More technically:

The spec requires that any Document being presented in a browsing context must implement the 
DocumentWindow interface, which inherits from the AbstractView interface, and that the defaultView 
attribute thus inherited must be the document's window object.

It also requires that if any document that *isn't* being presented in a browsing context implements the 
DocumentWindow interface, then the defaultView must be null.

 Ian Hickson questioned whether it makes sense to require this - I am not sure if it is good or not 
myself. I don't think we can necessarily require that such documents not implement DocumentWindow, 
since in browsers they'll likely be the same kind of object as presented documents.

(An example of non-presented documents would be the responseXML document of XMLHttpRequest.)

Sorry if this point is too obscure for anyone to really care about.
Received on Tuesday, 4 April 2006 09:23:15 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 8 January 2008 14:18:54 GMT