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.
