New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Selenium WebDriver for .Net does not work IE11 when WebComponents.js present #1765
Comments
Also reported in webcomponents/webcomponentsjs#504, since I am not sure if this is WebComponents.js issue or Selenium issue. |
Same problem with Selenium IEDriverServer 2.51.1 as well as Selenium Standalone Server 2.52 |
Selenium Standalone Server shows some stack trace:
|
This polyfill overrides basic DOM functionality, and causes JavaScript execution to return a wrapper object instead of the actual DOM node. Since IE doesn't have a native XPath-over-HTML engine, finding elements by XPath is done using a JavaScript XPath execution engine. Additionally, the automation atoms for finding elements are written in JavaScript, and that means finding by CSS selector similarly uses JavaScript, via |
Thank you for a clear response. I assume that there is no JavaScript bridge that I could use to make Selenium compatible with the polyfill in IE11? In my very brief look into IE Driver, I saw a mechanism of falling back to Sizzle for element finding. Isn't the WebComponents.js polyfill more or less the same thing? |
The Sizzle fall back is vestigial, and almost entirely unused. It will be removed from the project in July. Additionally, it's not entirely an apples-to-apples comparison, since (if memory serves) the Sizzle library returns the actual DOM object, not an object which wraps the DOM object and mimics its properties. |
Hi! I'm facing the exact same problem. Best, |
Unfortunately not. |
Closing this since the thread has been stale and also thanks to the explanation given here. |
Expected Behavior
WebDriver should be able to find an element on page.
Actual Behavior
WebDriver can't find an element on page if WebComponents.js is loaded and the browser is IE11. This happens at least for methods
By.XPath
andBy.CssSelector
.The below test project tries Firefox and IE11 driver. Only IE11 fails on this.
My environment is Windows 10 64-bit, using Selenium for .Net.
Versions used: NUnit 2.6.4, NUnitTestAdapter 2.0.0, Selenium.Support 2.52.0, Selenium.WebDriver 2.52.0, WebDriver.IEDriverServer.win64 2.44, WebComponents.js 0.7.21
Steps to reproduce
I have created a test project to recreate the issue: https://github.com/warpech/SeleniumTest
For example, the following test:
Fails with error:
The text was updated successfully, but these errors were encountered: