Some browsers - I can't remember witch - always return a status of 0 for the file: protocol, others don't return a value at all in that case, hence this hack.
We're going to be doing more work on Ajax for 1.6.1, but I'm not even sure there is a real solution ot his issue. Regards, Tobie On Nov 13, 3:29 am, tbeck <[EMAIL PROTECTED]> wrote: > On Nov 12, 6:52 pm, "Mislav Marohnić" <[EMAIL PROTECTED]> > wrote: > > > No browser is "violating the spec" because there is no spec for XHR, the > > document is only a working draft. So, status codes and ready states are not > > consistent cross-browsers. > > Fair enough. The real issue is that I'm not sure an undefined or 0 > status should result in success() returning true, regardless of how > XHR is supposed to work and what the browsers do. > > Tim --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Prototype: Core" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/prototype-core?hl=en -~----------~----~----~----~------~----~------~--~---
