-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
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
[🐛 Bug]: Invalid locator - GetShadowRoot and By.Xpath #12123
Comments
@jrod567, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
That error comes from Chrome directly, they need to support XPATH as well. More context #11893. Please raise this with the Chrome/ChromeDriver team. |
Hi, @jrod567. You can see if the feature is passing in the Web Platform Tests. If it is something new, please create an issue with the ChromeDriver team. |
Depending on your situation you might try:
|
Thank you!! Titus - that's helpful, much appreciated! |
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs. |
What happened?
When working with the shadowdom, using the By.XPath locator strategy is throwing an invalid locator unexpectedly.
Using other locators works fine and this is only an issue when working with IWebElement.GetShadowRoot() searchcontext.
How can we reproduce the issue?
Relevant log output
Operating System
Windows 10
Selenium version
4.8.1, 4.9.1
What are the browser(s) and version(s) where you see this issue?
Chrome v113.0.5672.127
What are the browser driver(s) and version(s) where you see this issue?
Latest
Are you using Selenium Grid?
Yes, 4.9.1
The text was updated successfully, but these errors were encountered: