- From: Anne van Kesteren <annevk@opera.com>
- Date: Mon, 01 Feb 2010 11:27:52 +0100
- To: "Jonas Sicking" <jonas@sicking.cc>
- Cc: "Ian Hickson" <ian@hixie.ch>, "Alexey Proskuryakov" <ap@webkit.org>, "WebApps WG" <public-webapps@w3.org>
On Mon, 01 Feb 2010 03:38:08 +0100, Jonas Sicking <jonas@sicking.cc> wrote: > On Sun, Jan 31, 2010 at 5:09 AM, Anne van Kesteren <annevk@opera.com> > wrote: >> On Wed, 16 Dec 2009 20:46:03 +0100, Jonas Sicking <jonas@sicking.cc> >> wrote: >>> 1. Update .responseText >>> 2. If readystate is not yet 3, set it to 3 and fire readystatechange >> >> This would dispatch readystatechange to often. The specification sides >> with >> IE/Opera here rather than WebKit/Gecko. > > Huh? This would only fire readystatechange for readyState=3 once per > request. That doesn't seem too often. My bad. I thought you meant to dispatch readystatechange regardless. >>> 3. Fire a 'progress', unless 'loadstart' or 'progress' has been fired >>> within the past 50ms >> >> This is already required elsewhere. I suppose I could try to merge the >> two, would that be useful? > > The main point of my email was that responseText should never change > other than from the main event loop. I.e. doing xhr.responseText == > xhr.responseText should always return true. Ok. That is definitely covered now. -- Anne van Kesteren http://annevankesteren.nl/
Received on Monday, 1 February 2010 10:28:31 UTC