Ajax.Responders test failing is a know issue due to behavior of the ActiveX XHR object.
All these (testing) issues will be addressed when Ajax is finally tested against a proper Webrick backend. That means no more testing Ajax without Ruby or over local "file:" scheme, but hey -- you couldn't even "compile" the framework without Ruby, either. -M On 1/25/07, Matti Ryhanen <[EMAIL PROTECTED]> wrote: > > I think that the IE-issues are there regardless of your patch. At least > the tests are failing for me without it too. > > On IE7 there will be issues with the tests when using the XHR on a local > file: URL, like the relative ones in the ajax.html tests, because the new > native IE7 XHR-object will not allow request to local url:s. > > The tests will run if the ActiveX XHR-object is loaded for all IE > versions, but I don't think this is a good solution since there seem to be > yet other issues with the ActiveX-object and IE7, and the Native IE7-object > should be used. > > The test for Ajax.Responders will fail even using the ActiveX object, and > from what I can tell, the two failed test there happen because IE and > firefox seem to fire readystatechanges for readyState 4 at different times. > I'm not sure this is much of an issue though, and maybe the tests should be > changed to reflect this? --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Ruby on Rails: Spinoffs" 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/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
