If a sleep fixes it, then it isn't the test library code or the driver, it has to do with when the app you are testing assigns the events to the elements. Is it angular or react? Essentially the test code is telling the driver to click before the app is ready, even though the element is displayed and enabled, etc. Unfortunately there isn't an easy fix for this. I have in the past implemented a click_until method that would check for the click doing what I wanted it to do and retrying if it didn't.
-- -- Before posting, please read https://github.com/watir/watir_meta/wiki/Guidelines-for-Posting-to-Watir-General-Google-Group. In short: search before you ask, be nice. watir-general@googlegroups.com http://groups.google.com/group/watir-general watir-general+unsubscr...@googlegroups.com --- You received this message because you are subscribed to the Google Groups "Watir General" group. To unsubscribe from this group and stop receiving emails from it, send an email to watir-general+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/watir-general/fd8d7ecd-77d1-4fab-92aa-f6bc57b16858%40googlegroups.com.
