Re: [qooxdoo-devel] Possible bug in phase of aborted requests (qx.io.request.Xhr)

2011-08-05 Thread Nicholas . Tindall
No probs, done :) Nick Tindall PASS Assets System & Information Services Division Department of Transport ph (03) 8688 1202 (ext 81202) mob 0413 177 761 Tristan Koch

Re: [qooxdoo-devel] Possible bug in phase of aborted requests (qx.io.request.Xhr)

2011-08-05 Thread Tristan Koch
Hi Nicholas, indeed, seems you've uncovered a bug. Can you please file a bug report? Regards Tristan Am 05.08.2011 um 08:04 schrieb : > Hi All, > > Actually the response value seems to be returned as an empty string not > undefined, here's another playground example that demonstrates the wro

Re: [qooxdoo-devel] Possible bug in phase of aborted requests (qx.io.request.Xhr)

2011-08-04 Thread Nicholas . Tindall
Hi All, Actually the response value seems to be returned as an empty string not undefined, here's another playground example that demonstrates the wrong phase value being returned after "loadEnd" is fired. http://goo.gl/rZGdN I have observed this behaviour in Chrome 13 and Firefox 5 Cheers,

[qooxdoo-devel] Possible bug in phase of aborted requests (qx.io.request.Xhr)

2011-08-04 Thread Nicholas . Tindall
Hi Guys, I've noticed some strange behaviour in qx.io.request.Xhr and I think it may be a bug. The documentation for the "getPhase" method says: When the requests is successful, it progresses the states: ‘unsent’, ‘opened’, ‘sent’, ‘loading’, ‘load’, ‘success’ In case of failure, the final s