On Thu, Jan 20, 2011 at 1:01 PM, vishnu wrote:
>
> Another idea I had was to in a wait block
> attachEventListener to document load a function of the form
> setTimeout(0, function(){}) and my attached function would set some
> element on the page and use watir to check for this element. This way
>
haha I was actually considering this, but here I can see the race
condition where the readystate might be complete before the onload
fires.
Another idea I had was to in a wait block
attachEventListener to document load a function of the form
setTimeout(0, function(){}) and my attached function wou
On Thu, Jan 20, 2011 at 12:06 PM, vishnu wrote:
> Ideally in the case of these redirects, I'd like to be able to check
> if watir believes the page is loaded AND if no javascript is currently
> executing, because I know that in this specific case, on none of my
> pages do I have to worry about jav
Hi Jarib
I understand what you mean about not being able to decide what
"finished" means in general, but tools could be provided to tell me if
something is finished in a specific case.
For example, there has been a lot of discussion about solving the
problems of waiting for ajax requests in gen
On Wed, Jan 19, 2011 at 8:31 PM, vishnu wrote:
>
> I posted an issue on github and jarib suggested I use something like
> wait_until_present to make sure I'm on the page I expect to be. But I
> have 2 concerns.
> firstly, even with wait_until_present is there a likelyhood I get a
> stale reference
Hi
I'm testing an application that integrates with a payment gateway.
This involves about 3 redirects. Each of these is not 302's but a page
that has a form and an onload script that submits the form via
javascript.
The problem is sometimes watir continues before the chain of
redirects. So somet
