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

Re: ISSUE-87: invoking open() when readyState is not 0, 1 or 4

From: Anne van Kesteren <annevk@opera.com>
Date: Tue, 14 Nov 2006 11:48:17 -0800
To: "Web APIs WG (public)" <public-webapi@w3.org>
Message-ID: <op.ti0umryc64w2qv@id-c0020>

On Fri, 10 Nov 2006 11:42:00 -0800, Anne van Kesteren <annevk@opera.com>  
wrote:
> Implementations seem to vary and it the results I get are not really  
> consistent. If anyone has a good way to test this please tell me.
>
> I have changed the editor's copy and I'm wondering if there are any  
> problems with the following text for implementors:
>
>    Invocations of this method when readyState is not 0
>    (Uninitialized) or 4 (Loaded) must be ignored.
>
>    Invoking this method when readyState is 4 (Loaded)
>    must be identical to when readyState is 0
>    (Uninitialized). Also, all members of the object
>    must be set to their initial values.

I changed this again based on feedback. Invoking open() should "reset" the  
object. As in, aborting any requests and setting all members to their  
initial values.

Only issue left open is event handlers which likely remain to exist.


-- 
Anne van Kesteren
<http://annevankesteren.nl/>
<http://www.opera.com/>
Received on Tuesday, 14 November 2006 19:48:53 GMT

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