23787 2013-11-11 05:18:31 +0000 Clarify that which HTTP entity body is referred in ProgressEvent spec 2013-11-25 14:05:14 +0000 1 1 1 Unclassified WebAppsWG XHR unspecified All All RESOLVED FIXED P2 normal --- 1 tyoshino annevk mike public-webapps public-webapps-bugzilla oldest_to_newest 96103 0 tyoshino 2013-11-11 05:18:31 +0000 In the definition of "fire a progress event named e", attributes are built from "HTTP entity body". This means "HTTP request entity body" for "Fire a progress event named progress on the XMLHttpRequestUpload object." while this means "HTTP response entity body" for "Fire a progress event named progress". It would be nice if this is made less implicit. 96106 1 annevk 2013-11-11 06:09:56 +0000 I guess we could have "fire an upload progress event" and "fire a progress event". Would that work? 96108 2 tyoshino 2013-11-11 06:14:23 +0000 (In reply to Anne from comment #1) > I guess we could have "fire an upload progress event" and "fire a progress > event". Would that work? Sounds good 96113 3 annevk 2013-11-11 08:59:04 +0000 https://github.com/whatwg/xhr/commit/8af96dd4157ba992b6730a3e24728677dd19929a 96684 4 tyoshino 2013-11-22 03:41:16 +0000 Thanks for the update, Anne, but the new text needs one fix. http://xhr.spec.whatwg.org/ > To fire an upload progress event named e means to fire an event named e with an event using the ProgressEvent interface that also meets these conditions: > > Initialize the loaded attribute to the length of request's body. > If the length of response's body is known through the Content-Length header, set the lengthComputable attribute value to true and the total attribute value to the length. "response" in the 2nd bullet point should be "request". 96775 5 annevk 2013-11-25 14:05:14 +0000 https://github.com/whatwg/xhr/commit/ab6ba77f2c559a5e23b0b28fa642d76e348e1330