W3C home > Mailing lists > Public > public-webapps@w3.org > October to December 2010

progress events in sync XHR not entirely ruled out

From: Eric Uhrhane <ericu@google.com>
Date: Wed, 24 Nov 2010 10:54:15 -0800
Message-ID: <AANLkTinM=XBCEwxU0XBzkTx=VGmxF1fLr9pCx3j=5UXZ@mail.gmail.com>
To: Anne van Kesteren <annevk@opera.com>
Cc: Web Applications Working Group WG <public-webapps@w3.org>
In the XHR2 spec, most references to progress events make it clear
that they're only sent for asynchronous XHRs.  However, in three
cases, the events aren't written as being exclusive to the async case.
 I'm guessing these are just oversights:

1) http://dev.w3.org/2006/webapi/XMLHttpRequest-2/#cross-origin-request-event-rules:

"The cross-origin request event rules are as follows:

If the cross-origin request status is preflight complete
Make upload progress notifications."

2) http://dev.w3.org/2006/webapi/XMLHttpRequest-2/#switch-done:

"When it is said to switch to the DONE state run these steps:
1. If the asynchronous flag is false update the response entity body.
2. Switch the state to DONE.
3. Dispatch a readystatechange event.
4. Dispatch a progress event called load.
5. Dispatch a progress event called loadend."

3) http://dev.w3.org/2006/webapi/XMLHttpRequest-2/#the-abort-method

However, if #1 and #2 are fixed, then there's no way to call the abort
method on a sync XHR anyway.

Received on Wednesday, 24 November 2010 18:55:01 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 18:13:13 UTC