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

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

From: Ian Hickson <ian@hixie.ch>
Date: Tue, 4 Apr 2006 23:05:11 +0000 (UTC)
To: Web APIs WG <public-webapi@w3.org>
Message-ID: <Pine.LNX.4.62.0604042259550.21459@dhalsim.dreamhost.com>

On Tue, 4 Apr 2006, Web APIs Issue Tracker wrote:
> 
> 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.

There are a number of other things on DocumentWindow that shouldn't be 
there in an XMLHttpRequest document as well. For example, 
document.location, document.designMode, document.execCommand, etc.

In any case if we want to _allow_ Document to implement DocumentWindow 
even when there's no Window, we should just require it, and be done with 
it. I don't want to end up in a situation where some browsers have it and 
some browsers don't.

-- 
Ian Hickson               U+1047E                )\._.,--....,'``.    fL
http://ln.hixie.ch/       U+263A                /,   _.. \   _\  ;`._ ,.
Things that are impossible just take longer.   `._.-(,_..'--(,_..'`-.;.'
Received on Tuesday, 4 April 2006 23:05:24 GMT

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