- From: Jonas Sicking <jonas@sicking.cc>
- Date: Thu, 18 Sep 2008 17:31:05 +0200
- To: "Sunava Dutta" <sunavad@windows.microsoft.com>
- Cc: "Anne van Kesteren" <annevk@opera.com>, "WebApps WG" <public-webapps@w3.org>, "Gideon Cohn" <gidco@windows.microsoft.com>, "Zhenbin Xu" <Zhenbin.Xu@microsoft.com>, "IE8 Core AJAX SWAT Team" <ieajax@microsoft.com>
On Wed, Sep 17, 2008 at 3:03 AM, Sunava Dutta <sunavad@windows.microsoft.com> wrote: > Jonas said >> I guess IE doesn't have an abort event on the XHR object (is this >> correct?) so the relation between ontimeout and onabort is undefined as >> far as the IE implementation goes. > > Correct. We do have abort and timeout, and adding onabort in the future IE release will have to be considered so we should define the relationship. As you mentioned, a possible good definition of timeouts is that a 'timeout' event should fire (which will trigger ontimeout) and then abort() should be called which will result in an 'abort' even (which will trigger onabort). Sounds good to me. Would be great to hear what other people think on having timeout in general and the specifics regarding what should happen when the timeout fires. / Jonas
Received on Thursday, 18 September 2008 15:31:39 UTC