The Internet Explorer Driver Revisited The Quickening
summary
IE WebDriver now requires ie_driver_server.exe is mandatory, so tests must point to that executable (cloud providers like Sauce Labs already ship it). Protected Mode checkboxes must match across all four zones or tests become flaky — avoid the “ignore protected mode” capability. Native events cause mouse race conditions via SendMessage; synthetic events work since ie_driver_server 2.26 (alerts no longer block), and requireWindowFocus introduced in 2.29.0 uses SendInput to reduce races but forces the browser to the foreground. Visual C++ ATL is currently required to build the driver.
AI-written summary · about
chapters (11)
- 0:00Start
- 1:00Jim Evans
- 12:25Redesign of the Website
- 13:32Windows Message Loop
- 16:16To Disable Native Events in the Ie Driver
- 18:34Require Window Focus
- 21:28What's Next
- 28:51Latency
- 31:36Is There any Solution for Self-Signed Certificates for Ie
- 32:37Why Does the Webdriver Api Not Support Http Status Codes
- 33:24Is Ie Driver Work Differently on Ie8 than Ie 9 and 10
related talks
36mBuilding a Driver: Lessons Learned from Developing the Internet Explorer Driver
22mClosing Keynote
30mBrowser Testing
49mSelenium: state of the union
31mRevolutionising Browser Automation: A Deep Dive into the WebDriver BiDi Project and...- 31mRevolutionising Browser Automation: A Deep Dive into the WebDriver BiDi Project and its Integration with Selenium
48mThe Nuts and Bolts of WebdriverIO
23mLife After Selenium