-
-
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]: "detached shadow root" not translated to DetachedShadowRootException #13580
Comments
@joerg1985, 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! |
the same issue should exist for "insecure certificate" -> |
The java client has been fixed in 1cdf5b4 |
You motivated me, fixed in .net too: 8405299 |
Can we close this? |
@nvborisenko i think the "insecure certificate" -> InsecureCertificateException is still missing in c#? @diemol When searching for "detached shadow root" in the repo i can only find c# / java / js code, so probably other bindings are still missing this? |
@titusfortner, do you know? |
guessing this got added to spec and not updated in our code |
@titusfortner @p0deje would you let me know if adding the extra test here #14267 is enough in this case? And if it is and the PR gets merged, could we remove the C-rb label? I'm trying to go through all the ruby open bugs and it helps me to filter better, thank you so much 👍 |
What happened?
When using a detached shadow root a DetachedShadowRootException should be raised.
I am pretty sure this happens because the
ErrorHandler
does still use the none W3CErrorCodes
.It should use
ErrorCodec
to decode the error, this will allow to find the newer W3C errors.How can we reproduce the issue?
Relevant log output
Operating System
win 10 x64
Selenium version
4.18.0-SNAPSHOT
What are the browser(s) and version(s) where you see this issue?
chrome 121
What are the browser driver(s) and version(s) where you see this issue?
chromedriver 121.0.6167.85
Are you using Selenium Grid?
no
The text was updated successfully, but these errors were encountered: