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: Jonas Sicking <jonas@sicking.cc>
Date: Wed, 05 Apr 2006 17:39:19 -0700
Message-ID: <44346337.8090103@sicking.cc>
To: Boris Zbarsky <bzbarsky@mit.edu>
Cc: Ian Hickson <ian@hixie.ch>, Maciej Stachowiak <mjs@apple.com>, Web APIs WG <public-webapi@w3.org>

Boris Zbarsky wrote:
> Ian Hickson wrote:
>>> 3) Forbid any non-presented Document to implement DocumentWindow 
>>> (seems too
>>> restrictive).
>>
>> I am strongly in favour of 3. If we don't do 3, we're going to have to 
>> require a whole heck more than 1 -- we're going to have to special 
>> case every single API that requires a rendering context.
> 
> What happens when a document goes from "presented" to "non-presented" or 
> vice versa?
> 
> And note that even if we disallow such transitions doing what you 
> propose would require that all document creations know whether the 
> document is going to be presented.....  This could be a pretty heavy 
> burden in some cases.

Actually, it already does happen in some cases. If you hold on to a 
document inside an iframe and then navigate away from the document the 
document goes from being presented to being non-presented.

/ Jonas
Received on Thursday, 6 April 2006 00:39:29 GMT

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