- From: Anne van Kesteren <annevk@annevk.nl>
- Date: Fri, 30 Aug 2013 12:06:21 +0100
- To: Takeshi Yoshino <tyoshino@google.com>
- Cc: "Web Applications Working Group WG (public-webapps@w3.org)" <public-webapps@w3.org>
On Thu, Aug 1, 2013 at 6:13 PM, Anne van Kesteren <annevk@annevk.nl> wrote: > On Tue, Jul 30, 2013 at 10:25 AM, Takeshi Yoshino <tyoshino@google.com> wrote: >> Change on 2010/09/13 >> http://dev.w3.org/cvsweb/2006/webapi/XMLHttpRequest-2/Overview.src.html.diff?r1=1.138;r2=1.139;f=h >> reversed the order of event firing for "request error" algorithm and send() >> method to XHRUpload-then-XHR. >> >> send() (only loadstart event) and abort() method are still specified to fire >> events in XHR-then-XHRUpload order. Is this intentional or we should make >> them consistent? > > We should make them consistent in some manner. Firing on the main > object last makes sense to me. It also makes some amount of conceptual > sense to do the reverse for when the fetching starts, but I feel less > strongly about that. Anyone opinions on this? Would be good to sort out and I don't really care one way or another. -- http://annevankesteren.nl/
Received on Friday, 30 August 2013 11:06:48 UTC