Open GaurangTandon opened 2 hours ago
@GaurangTandon, thank you for creating this issue. We will troubleshoot it as soon as we can.
Triage this issue by using labels.
If information is missing, add a helpful comment and then I-issue-template
label.
If the issue is a question, add the I-question
label.
If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted
label.
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable G-*
label, and it will provide the correct link and auto-close the
issue.
After troubleshooting the issue, please add the R-awaiting answer
label.
Thank you!
What happened?
Here's a video showing the issue: https://www.loom.com/share/1101be1e1c1a4770a439cf0041c5c882
Plain text output log for your convenience:
Based on how Selenium has always behaved, I believe this new behavior on Chrome 131 is a regression. Running
document.getElementById('root').shadowRoot
still returnsnull
in Chrome 131, so I think this might be a Selenium issue rather than Chrome issue. Please do let me know if it's otherwise and I will report it on bugs.chromium.org/p/chromedriverHow can we reproduce the issue?
Python code:
HTML file:
Install selenium and run
python runtest.py
two times, once with thebinary_location
set to Chrome beta (as it is right now) and other without it (so it runs stable version). The video shows the step clearly.Relevant log output
When I put
at the top of the Python file above, I don't get any logs output on the terminal.
Operating System
macOS
Selenium version
4.25.0
What are the browser(s) and version(s) where you see this issue?
Chrome 131 beta
What are the browser driver(s) and version(s) where you see this issue?
(automatically downloaded by Selenium)
Are you using Selenium Grid?
No response