I think Oscar is correct in his assessment that this likely comes down to a difference in how the underlaying webdriver layer communicates with the browser compared to how Watir does it.
This difference has sometimes resulted in situations where while webdriver seems to work very well on Firefox and Chrome, the ability to drive IE is sometimes seen as 'lacking'. This is one reason that we've kept the classic version of Watir around, because in some situations it's use of the Win32 OLE/COM to communicate with the browser seems to yield better results than Webdriver. If you really want to get into it, there is a fairly good description of the selenium-webdriver driver for IE here: http://www.aosabook.org/en/selenium.html Some users have chosen to deal with this by using Watir when driving IE, and Watir-webdriver for Chrome and FF. Watir 3.x makes this a lot easier by bringing the watir API up to date and into much better alignment with watirspec and watir-webdriver. (However keeping these two in sync is a tall order since there is no mandate that if a feature is added to WW (such as the new .alert methods) that it also be added to Watir-classic or vise-versa. On Wednesday, June 13, 2012 8:50:35 AM UTC-7, Ben Armstrong wrote: > > On 13/06/12 12:15 PM, Oscar Rieken wrote: > > I am going to say yes this is my assumption based on the fact watir > > itself uses the win32-api-1.4.8.gem which I am guessing gives it the > > ability to know the browser and native OS events a bit better > > https://github.com/djberg96/win32-api > > but as far as the original problem of it not waiting for the browser > > to load I am going again to guess there is probably a way to hook into > > the events happening on the page to check if its done or not (but > > that's just me) > > If I understood my colleague's Javascript code which is several years > old, is multilayered, including its own browser compatibility layer for > event handling pre-dating the modern alternatives ... and why we can't > just use an out-of-the-box solution (jQuery-based?) here instead ... > Yes, I could probably come up with a patch in the events. Maybe I should > just punt the whole problem back to her. But meanwhile, I have a > satisfying enough answer that the team accepts and I can continue on > with watir-webdriver implementing a workaround in whatever way I see fit > for the short term. Yay. Mission accomplished! > > Thanks so much for your help, and to Chuck as well for his input. > > Ben > > -- Before posting, please read http://watir.com/support. In short: search before you ask, be nice. [email protected] http://groups.google.com/group/watir-general [email protected]
