You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
What should the ProgressEvent attributes be in the case of an error/abort? #14
changed the title [-]What should the ProgressEvent attributes be in the case of an error?[/-][+]What should the ProgressEvent attributes be in the case of an error/abort?[/+]on Jul 20, 2015
The same questions apply to any progress event it seems. Not even for progress progress events is it mentioned what any of the attributes of the event should be initialized to.
I'll try to write some tests to figure out what browser currently are doing (from looking at the code it seems chrome at least always includes whatever information is has available with any event, so abort and error events include how much data has been read before the abort/error occurred).
You might also want to check https://xhr.spec.whatwg.org/ and align to some extent if possible, although maybe trying to go for that is just a waste of time.
Ah yeah, at least in theory it would make sense to behave the same as XHR. In which case it seems that most non-progress progress events (such as abort, error, etc) set their attributes to zero (which isn't what the chrome implementation does, even for XHR btw).
Activity
jdm commentedon Jul 20, 2015
The same questions are true for the progress events fired from the abort steps.
[-]What should the ProgressEvent attributes be in the case of an error?[/-][+]What should the ProgressEvent attributes be in the case of an error/abort?[/+]mkruisselbrink commentedon Feb 3, 2017
The same questions apply to any progress event it seems. Not even for
progressprogress events is it mentioned what any of the attributes of the event should be initialized to.I'll try to write some tests to figure out what browser currently are doing (from looking at the code it seems chrome at least always includes whatever information is has available with any event, so abort and error events include how much data has been read before the abort/error occurred).
annevk commentedon Feb 7, 2017
You might also want to check https://xhr.spec.whatwg.org/ and align to some extent if possible, although maybe trying to go for that is just a waste of time.
mkruisselbrink commentedon Feb 7, 2017
Ah yeah, at least in theory it would make sense to behave the same as XHR. In which case it seems that most non-progress progress events (such as abort, error, etc) set their attributes to zero (which isn't what the chrome implementation does, even for XHR btw).