unfortunately, this won't be testable publicly, i know how much that would help. and of course, I know no other sites that have a similar setup.
I'm going to take a look into the whole readyState=interactive solutions i've found and see if that helps at all. On May 11, 4:52 pm, Charley Baker <[email protected]> wrote: > Give us an example from a public site and your script? Most of this has been > solved already if you look through the list, but any specific examples we > can take a look at and make it better. > > Charley Baker > Lead Developer, Watir,http://watir.com > > On Wed, May 11, 2011 at 3:43 PM, CLARKETRON3000 <[email protected]>wrote: > > > > > > > > > i have my own checks in place to wait for elements on the screen that > > i know are going to be there, but this seems to be part of the > > internal framework of watir that is blowing up on me. my own code has > > no dependency on readyState, i'm just using the rescue clause as a > > work around until i can figure out what's going on > > > On May 11, 3:32 pm, Charley Baker <[email protected]> wrote: > > > It's not a wise idea to depend on that. Instead look for the controls and > > > elements you expect to have after the event occurs. There are several > > posts > > > in the group and actually several frameworks that leverage this > > mechanism. > > > Unfortunately readystate is really not a guarantee that the browser is > > > actually ready in this case. > > > > HTH, > > > > Charley Baker > > > Lead Developer, Watir,http://watir.com > > > > On Wed, May 11, 2011 at 3:27 PM, CLARKETRON3000 <[email protected] > > >wrote: > > > > > the rescue clause is recording the readyState as interactive > > > > i'm capturing the readystate to an array and doing a puts on the array > > > > afterwards (thanks for the help paul) > > > > > On May 11, 3:19 pm, CLARKETRON3000 <[email protected]> wrote: > > > > > update: > > > > > i am at least getting around this issue for the time being by putting > > > > > a rescue clause on my call to the submit button. from there, I am > > > > > spitting out the doc.readyState, but I suspect that by the time it's > > > > > actually displaying the readyState, it has resolved, otherwise it > > > > > wouldn't be running into this issue in the first place(???) > > > > > > On May 11, 2:45 pm, CLARKETRON3000 <[email protected]> wrote: > > > > > > > I checked through the discussions here, and there are two jira > > tickets > > > > > > around ready state 446 and 466 that I could find, but neither > > really > > > > > > seemed to address this issue. > > > > > > > The error occurs on the website I'm testing on a form submit. > > There > > > > > > is also a javascript call that occurs if the submit takes longer > > than > > > > > > 3 seconds, an overlay "loading" image loads onto the screen. The > > > > > > error is intermittent, and not reliably reproducible but seems to > > > > > > occur more frequently on the times that the JS call occurs. > > > > > > > i'm using Watir 1.8.0, and IE8. > > > > > > here is the important parts of the stack: > > > > > > Exception:unknown property or method: `readyState' > > > > > > HRESULT error code:0x80004005 > > > > > > Unspecified error > > > C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.8.0/lib/watir/ie-class.rb: > > > > > > 511:in `method_missing' > > > C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.8.0/lib/watir/ie-class.rb: > > > > > > 511:in `block in wait' > > > > > > C:/Ruby192/lib/ruby/1.9.1/timeout.rb:57:in `timeout' > > > C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.8.0/lib/watir/ie-class.rb: > > > > > > 489:in `wait' > > > C:/Ruby192/lib/ruby/gems/1.9.1/gems/watir-1.8.0/lib/watir/element.rb: > > > > > > 231:in `click' > > > > > > > I have tried doing a bit of debugging at least to see what's > > > > > > happening, adding a puts doc.readyState inside the until loop on > > line > > > > > > 511, but to no avail. It always comes back with complete or > > loading > > > > > > when it works, and when it gets the exception, i don't get the > > print > > > > > > out. > > > > > -- > > > > Before posting, please readhttp://watir.com/support. In short: search > > > > before you ask, be nice. > > > > > [email protected] > > > >http://groups.google.com/group/watir-general > > > > [email protected] > > > -- > > Before posting, please readhttp://watir.com/support. In short: search > > before you ask, be nice. > > > [email protected] > >http://groups.google.com/group/watir-general > > [email protected] -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. [email protected] http://groups.google.com/group/watir-general [email protected]
