This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
the update attribute needs to be better described to communicate a sense of its intended purpose; at present, section 4.7.5 only says "The upload attribute must return the associated XMLHttpRequestUpload object." it says nothing about the function of the XMLHttpRequestUpload object and why, for example, there needs to be two distinct XMLHttpRequestEventTargets; furthermore, the spec should state that the upload objects are distinct across different XMLHttpRequest objects (at the moment, this seems merely to be assumed); i.e., each distinct XMLHttpRequestUpload object is associated with a distinct XMLHttpRequest object
s/update/upload/g
http://dvcs.w3.org/hg/xhr/rev/ba9735a82582 By the way, many thanks for all these reports!
(In reply to comment #2) > http://dvcs.w3.org/hg/xhr/rev/ba9735a82582 You added a note: "As indicated earlier, each XMLHttpRequest object has an associated XMLHttpRequestUpload object." But this doesn't address my comment about whether XMLHttpRequestUpload objects are distinct or not; i.e., an implementer might (for whatever reason) reuse the same upload object on more than one request object. [You ask why? Because the spec allows this, or at least doesn't preclude this.] It would be better if the word "distinct" were added in 4.7, i.e., "Each XMLHttpRequest object also has a distinct, associated XMLHttpRequestUpload object."
https://github.com/whatwg/xhr/commit/1d7f7d3a9a38bb7fc830f4eb365697cbed21db13 Used "unique".
thanks