Changes between Version 1 and Version 3 of Ticket #15372
- Timestamp:
- May 17, 2012, 3:33:51 PM (9 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
Ticket #15372 – Description
v1 v3 11 11 One possible fix is to go back to checking protocol, since status:0 should only be valid for certain protocols like file:. Unfortunately, this is a slippery slope, as there are a bunch of specialized protocols and situations where status:0 is ok, like appcache. Not sure exactly why we stopped checking protocol, but that may be one reason. It was also very verbose code. 12 12 13 Another possible fix is to use !ProgressEvent (XHR2?) at least where it is available. It would be good to fix this on dojo.xhr, even if dojo.request solves the problem. We're using the {{{/dojo/io/error}}} event, and xhr is obviously used a lot.13 Another possible fix is to use !ProgressEvent (XHR2?) at least where it is available. It would be good to fix this on dojo.xhr, even if dojo.request solves the problem. We're using the {{{/dojo/io/error}}} topic, and xhr is obviously used a lot. 14 14 15 15 This is likely a regression from whenever we changed the {{{_isDocumentOk}}} code.