- From: <bugzilla@jessica.w3.org>
- Date: Fri, 05 Sep 2014 13:03:23 +0000
- To: public-webapps@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26736
Bug ID: 26736
Summary: Does the final progress event need to be dispatched
after readystatechange?
Product: WebAppsWG
Version: unspecified
Hardware: PC
OS: Linux
Status: NEW
Severity: normal
Priority: P2
Component: XHR
Assignee: annevk@annevk.nl
Reporter: tyoshino@google.com
QA Contact: public-webapps-bugzilla@w3.org
CC: mike@w3.org, public-webapps@w3.org
Related to bug25587 but about successful case.
http://xhr.spec.whatwg.org/#handle-response-end-of-file
It's specified that XHR must fire the final progress event after
readystatechange.
Anne's comment about this change is here:
http://lists.w3.org/Archives/Public/public-webapps/2011OctDec/1712.html
Anne, what you had to do is to dispatch a progress event with loaded and total
at the point we received all data. It's ok that the final progress event is
dispatched before readystatechange dispatch as long as its loaded and total
represent all data. Right?
Commits:
- https://dvcs.w3.org/hg/xhr/rev/5c90cb13ad25
- https://github.com/whatwg/xhr/commit/f1c744d6cb74371bbbaa4c07f17bfa9e9caa1718
FYI, here's the result of event order checking for Chrome, Firefox and IE.
https://code.google.com/p/chromium/issues/detail?id=409544#c1
--
You are receiving this mail because:
You are on the CC list for the bug.
Received on Friday, 5 September 2014 13:03:29 UTC