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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
Hmmm, yes I think we''ll need to see some syntax... -- Matt Foster Ajax Engineer Nth Penguin, LLC http://www.nthpenguin.com On Jun 24, 11:46 pm, Paul <pkm...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> 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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
LOL ... we actually run into the same problem as we reported before (see http://prototype.lighthouseapp.com/projects/8886/tickets/12-ns_error_not_available-during-ajax-requests, which is fixed for 1.6.0.3). However, we accidentally upgraded prototype which removed our patch. No one realized we are running into the same exact issue since we assumed we already had the patch :). On Jun 25, 6:23 am, Matt Foster <mattfoste...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> Hmmm, yes I think we''ll need to see some syntax... > > -- > Matt Foster > Ajax Engineer > Nth Penguin, LLChttp://www.nthpenguin.com > > On Jun 24, 11:46 pm, Paul <pkm...-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote: > > > 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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---
It''s better if you can "monkey patch" if possible - load an external script that patches Prototype with your fix after it''s been loaded. Not that a Prototype upgrade will never cause your patch to break, but in many cases, it won''t, and in the case of a big upgrade you''ll probably end up having to tweak your patch anyway. -Fred On Wed, Jun 25, 2008 at 12:26 PM, Paul <pkmiec-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:> > LOL ... we actually run into the same problem as we reported before > (see > http://prototype.lighthouseapp.com/projects/8886/tickets/12-ns_error_not_available-during-ajax-requests > , > which is fixed for 1.6.0.3). However, we accidentally upgraded > prototype which removed our patch. No one realized we are running into > the same exact issue since we assumed we already had the patch :).-- Science answers questions; philosophy questions answers. --~--~---------~--~----~------------~-------~--~----~ 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-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org To unsubscribe from this group, send email to rubyonrails-spinoffs-unsubscribe-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org For more options, visit this group at http://groups.google.com/group/rubyonrails-spinoffs?hl=en -~----------~----~----~----~------~----~------~--~---