Anne van Kesteren wrote: > The constructor and providing a pointer to the document from the object > on which the constructor was invoked. So correct me if I'm wrong, but wouldn't it work to say that if the object the constructor is on is a Window things work as now and otherwise whatever specification placed the constructor on some other object is responsible for describing how one gets a document from that object? Note that a lot of the text can still be shared (in terms of whether the calling scope or callee object determines the "right" document to use); all that depends on Window is how one actually gets the document, right? > Having basic Window support is also good for the test suite so we can > actually test the cross-frame scenarios you raised a long time ago (for > which I added this dependency when I addressed the issue). I don't see a problem with saying that the test suite requires a Window, to be honest. If we really wanted we could somehow flag the tests in the test suite that really have that as a hard requirement, of course, but realistically the tests are HTML files, aren't they? So they would always have a Window... -BorisReceived on Tuesday, 17 June 2008 15:48:29 GMT
This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 18:49:26 GMT