This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 23787 - Clarify that which HTTP entity body is referred in ProgressEvent spec
Summary: Clarify that which HTTP entity body is referred in ProgressEvent spec
Status: RESOLVED FIXED
Alias: None
Product: WebAppsWG
Classification: Unclassified
Component: XHR (show other bugs)
Version: unspecified
Hardware: All All
: P2 normal
Target Milestone: ---
Assignee: Anne
QA Contact: public-webapps-bugzilla
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-11-11 05:18 UTC by Takeshi Yoshino
Modified: 2013-11-25 14:05 UTC (History)
2 users (show)

See Also:

Attachments

Description Takeshi Yoshino 2013-11-11 05:18:31 UTC 
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.
Comment 1 Anne 2013-11-11 06:09:56 UTC 
I guess we could have "fire an upload progress event" and "fire a progress event". Would that work?
Comment 2 Takeshi Yoshino 2013-11-11 06:14:23 UTC 
(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
Comment 4 Takeshi Yoshino 2013-11-22 03:41:16 UTC 
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".