Actually, I found a workaround of sorts -
In my tests, I would grab a div and assign it to a variable and use that variable throughout. The problem was, during the operations after the var assignment, I would do some things that would cause postbacks. And, any references after those postbacks seemed to have lost all context.
Removing the variable assignment and references and just calling straight to div() fixed all the issues.
Very interesting, though. I’m not sure if this would be considered a bug, or a normal practice that I should watch out for going forward.
On 9/15/06 4:07 AM, "Angrez Singh" <[EMAIL PROTECTED]> wrote:
Hi Bret,
I agree that the bug was related to 'to_s' method but this method internally calls 'text' method which was the source of error that I have logged.
Thanks for pointing to the URL on 'openqa'.
Regards,
Angrez
On 9/15/06, Bret Pettichord <[EMAIL PROTECTED]> wrote:
Angrez,
I'm pretty sure that the bug you cite only affected the "to_s" method
and not the "text" method. I don't think it relates to Jason's issue.
We've migrated all the defects to Jira. Here is the current reference:
http://jira.openqa.org/browse/WTR-33
Bret
Angrez Singh wrote:
> 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 <http://rubyforge.org/tracker/index.php?func=detail&aid=2978&group_id=104&atid=487>
> <http://rubyforge.org/tracker/index.php?func=detail&aid=2978&group_id=104&atid=487 <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
_______________________________________________
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
_______________________________________________ Wtr-general mailing list [email protected] http://rubyforge.org/mailman/listinfo/wtr-general
