What happened?
The InvalidSelectorException in Java derives from NoSuchElementException, a FluentWait will retry until the timeout is reached.
The InvalidSelectorException in C# derives from NoSuchElementException, a WebDriverWait will retry until the timeout is reached.
The InvalidSelectorException in Python derives from WebDriverException, a wait will instantly fail.
This is confusing in my mind, is it correct to derive InvalidSelectorException from NoSuchElementException?
Will a invalid selector, repair it self over time?
How can we reproduce the issue?
search By.xpath("]") using a FluentWait / WebDriverWait / wait
Relevant log output
Operating System
Windows 10 x64
Selenium version
4.x.x
What are the browser(s) and version(s) where you see this issue?
N/A
What are the browser driver(s) and version(s) where you see this issue?
N/A
Are you using Selenium Grid?
No response
What happened?
The InvalidSelectorException in Java derives from NoSuchElementException, a FluentWait will retry until the timeout is reached.
The InvalidSelectorException in C# derives from NoSuchElementException, a WebDriverWait will retry until the timeout is reached.
The InvalidSelectorException in Python derives from WebDriverException, a wait will instantly fail.
This is confusing in my mind, is it correct to derive InvalidSelectorException from NoSuchElementException?
Will a invalid selector, repair it self over time?
How can we reproduce the issue?
Relevant log output
Operating System
Windows 10 x64
Selenium version
4.x.x
What are the browser(s) and version(s) where you see this issue?
N/A
What are the browser driver(s) and version(s) where you see this issue?
N/A
Are you using Selenium Grid?
No response