[xhr] remove readystatechange event fired while invoking async send()?

In step eight of the send() method a substep fires a readystatechange  
event while the state of the object does not actually change. Internet  
Explorer and Firefox implement this, Safari, Chrome, and Opera do not. It  
would be somewhat cleaner if we remove it as then readyState would go  
1,2,3,4 rather than 1,1,2,3,4. And it seems we can remove it given that in  
six years nobody felt the need to become interoperable on this.

Objections?


-- 
Anne van Kesteren
http://annevankesteren.nl/

Received on Thursday, 23 February 2012 08:40:55 UTC