I'm running into an intermittent problem in my selenium tests. It appears that respondToReadyState is invoked with readyState of 4, but this.transport.readyState is still 1. This results in a call to success(), which in turns calls this.transport.status which throws an exception with NS_ERROR_NOT_AVAILABLE.
With help of firebug, I can see that readyState and this.transport.readyState are different quite often in respondToREadyState. So, I assume that's the desired behavior. However, it seems like there is a race condition that in certain cases causes this.transport.status to fail. I'm using Prototype 1.6.0.1 and Firefox 2.0.0.14. I can provide additional debug info if someone can help. --~--~---------~--~----~------------~-------~--~----~ 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 rubyonrails-spinoffs@googlegroups.com 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 -~----------~----~----~----~------~----~------~--~---
