Hi Jason,

I think its a bug in the watir 1.4.1 code where the function 'innerText' is called instead of function 'text' while setting or getting the text of the element. Please check the following URL for more details.

http://rubyforge.org/tracker/index.php?func=detail&aid=2978&group_id=104&atid=487

You can use watir 1.5 to get rid of this error or can manually change your 'watir.rb' file to reflect the changes. You need to change 'element' class and in that you need to change 'text' function. In that function just change 'innerText' to 'text' it should work. BTW, this is not a recommended method to get rid of error, you should get new copy of Watir.

- Angrez

On 9/15/06, David Schmidt <[EMAIL PROTECTED]> wrote:
Jason, check out
http://forums.openqa.org/thread.jspa?threadID=4012&tstart=0 for a
routine I use to wait for a page to load, checking for possible popups
at the same time. It uses Watir::until_with_timeout. See if that helps.

David

Jason Alexander wrote:
>
> Doing some Googling, it appears that this has to do with the page
> still loading? Which makes sense, I have a few elements that are
> causing the page to "postback" (mechanism in ASP.NET).
>
> Assuming that's the problem, what's the best solution in most cases? I
> saw where there was some talk of a wait_until in Jira, but what can I
> do meanwhile?
>
> Thanks,
>
> -Jason
>
_______________________________________________
Wtr-general mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-general

_______________________________________________
Wtr-general mailing list
[email protected]
http://rubyforge.org/mailman/listinfo/wtr-general

Reply via email to