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

ISSUE-58: XMLHttpRequest.abort() should just reset the object

From: Web APIs Issue Tracker <dean+cgi@w3.org>
Date: Mon, 3 Apr 2006 11:46:52 +0000 (GMT)
To: public-webapi@w3.org
Message-Id: <20060403114652.C835D33207@kearny.w3.org>


ISSUE-58: XMLHttpRequest.abort() should just reset the object

http://www.w3.org/2005/06/tracker/webapi/issues/58

Raised by: Anne van Kesteren
On product: XMLHttpRequest

For some reason we resolve that abort() should do:

  Calling this method MUST cancel any network activity for which
  the object is responsible. In addition, UAs MUST then set
  readyState  to 4 (Loaded), call the function defined in
  onreadystatechange and reset the object.

http://groups.google.com/group/mozilla.dev.tech.xml/browse_thread/thread/74257e17b66e68e8/8e0b8aded9bac4a0
points out that only Mozilla has a funny implementation like that where all
other implementations just reset the object. I suggest we change the
specification to:

  Calling this method MUST cancel any network activity for which
  the object is responsible and reset the object.

... of course, we should define somewhere what it means for an object to be
resetted. The authoring guidelines can say something like:

  Some implementations, when calling abort(), set readyState to
  4, call onreadystatechange and reset the object instead of
  resetting the object directly as the specification requires.
Received on Monday, 3 April 2006 11:47:14 GMT

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