W3C home > Mailing lists > Public > public-webapi@w3.org > November 2007

Re: Window pointer

From: Bjoern Hoehrmann <derhoermi@gmx.net>
Date: Mon, 19 Nov 2007 15:28:15 +0100
To: "Anne van Kesteren" <annevk@opera.com>
Cc: "Web API WG (public)" <public-webapi@w3.org>
Message-ID: <sp53k3teq8btf179eds0g5gm52uj9loqnf@hive.bjoern.hoehrmann.de>

* Anne van Kesteren wrote:
>On Sat, 17 Nov 2007 00:31:24 +0100, Subbu Allamaraju  
><subbu.allamaraju@gmail.com> wrote:
>> But this can be done without requiring that "a persistent pointer to the
>> associated Window object must be stored on the newly created object". An
>> implementation can store whatever it needs to resolve the URI argument.
>> Isn't the requirement on the resolution and not on storing the pointer?
>I'm not sure what you mean.

The question is whether an implementation that does not store a Window
pointer is non-conforming even if it resolves URIs as required. E.g.,
XHR objects may have some private baseURI property which is updated if
the associated Document's baseURI changes. That would ensure URIs are
resolved correctly while allowing implementations to free the resources
associated with the original Window. You would not be able to tell the
difference from the outside, so the "MUST store Window pointer" is not
generally testable, and untestable requirements create confusion as we
have it here. Clearly such an implementation should be conforming.
Björn Höhrmann · mailto:bjoern@hoehrmann.de · http://bjoern.hoehrmann.de
Weinh. Str. 22 · Telefon: +49(0)621/4309674 · http://www.bjoernsworld.de
68309 Mannheim · PGP Pub. KeyID: 0xA4357E78 · http://www.websitedev.de/ 
Received on Monday, 19 November 2007 14:28:30 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 21:16:24 UTC