Thomas Milne wrote:
I've recently run into an issue where using Selenium to click a button
where onclick="Widget(this).nextCard()" causes Selenium to hang with the
Javascript error "element.parentNode has no properties". It looks like
something in Selenium is changing the value of 'this'- could anyone
point me in the right direction of what needs to be changed in order to
fix it? Or if it's fairly simple and somebody wants to have a crack at
patching it we'd love to test it for you!
Hi Thomas.
It's possible that Selenium isn't setting the context-object correctly
when it invokes onclick. Having said that, I've looked at the code
concerned, and can't see any obvious problems.
Whether you're keen to tackle this yourself, or are hoping someone else
will solve it, can you log the bug at
http://jira.public.thoughtworks.org/browse/SEL
Info to include in the report:
- What's your browser?
- If "this" doesn't point to the element you expect, can you determine
what it DOES refer to?
--
cheers, MikeW http://www.dogbiscuit.org/mdub/
_______________________________________________
Selenium-users mailing list
Selenium-users@lists.public.thoughtworks.org
http://lists.public.thoughtworks.org/mailman/listinfo/selenium-users
