- From: <bugzilla@jessica.w3.org>
- Date: Fri, 05 Sep 2014 18:18:01 +0000
- To: public-webapps-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=26736 --- Comment #2 from Glenn Maynard <glenn@zewt.org> --- I think it's fine if the final progress event is fired earlier. The important thing is that a "100% complete" progress event is always sent. If it's fired before readystatechange, it should be before state is set to DONE, so we don't have an event between the state change and the readystatechange event. I think I'd put it after step 3 ("If response is a network error..."). That way, setting the final response body (step 4) and switching to DONE (step 5) are still atomic to scripts, there are still no events between DONE and readystatechange, and this progress event happens in the same state as the other ones. It's just a last-minute progress event before any of the real end of file state changes start to happen. -- You are receiving this mail because: You are the QA Contact for the bug.
Received on Friday, 5 September 2014 18:18:02 UTC