Hi all
I just started playing with Selenium this week, and I'm pretty excited
about it (if you listened to Luke Closs's selenium podcast on
qapodcast.com, I was the QA engineer he quoted near the end).
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!
Thanks
-Thomas
_______________________________________________
Selenium-users mailing list
Selenium-users@lists.public.thoughtworks.org
http://lists.public.thoughtworks.org/mailman/listinfo/selenium-users
