So apparently the reason selenium was not seeing my DOM changes was that selenium uses _javascript_'s asynchronous event dispatch. So my DOM changes were being made, just not quickly enough for the asserts() to behave as expected.

I am new to _javascript_; as near as I can tell from experience and from research, synthetic JS events sent via dispatchEvent() are asynchronous. Since selenium relies on such synthetic events, its value is limited when constructing tests such as the one I attempted. Is there an alternative way to dispatch events synchronously? Integrating synchronous events into Selenium would make it *much* more useful, IMO. I know there are the various *AndWait() actions, but those are designed for a narrow purpose - waiting for the page to reload.

- Rick
_______________________________________________
Selenium-users mailing list
Selenium-users@lists.public.thoughtworks.org
http://lists.public.thoughtworks.org/mailman/listinfo/selenium-users

Reply via email to