Changes between Version 1 and Version 3 of Ticket #15372


Ignore:
Timestamp:
May 17, 2012, 3:33:51 PM (8 years ago)
Author:
Adam Peller
Comment:

Legend:

Unmodified
Added
Removed
Modified

  • Ticket #15372 – Description

    v1 v3  
    1111One 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.
    1212
    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.
     13Another 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.
    1414
    1515This is likely a regression from whenever we changed the {{{_isDocumentOk}}} code.