Hey! Had the same problem with chrome driver version 125.0.6422.142.
Turns out it’s a known issue in the Chromium bug tracker. Some folks are reporting it’s related to shadow DOM interactions.
If you’re dealing with shadow DOM, try using `driver.execute_script` to force clicks instead of the regular Selenium methods.
Otherwise, rolling back is the way to go for now.
Turns out it’s a known issue in the Chromium bug tracker. Some folks are reporting it’s related to shadow DOM interactions.
If you’re dealing with shadow DOM, try using `driver.execute_script` to force clicks instead of the regular Selenium methods.
Otherwise, rolling back is the way to go for now.
