InvalidSelectorException has changed

Fri, 21 Apr 2023 00:00:00 +0000

Before Selenium 4.8.2 in Java and C#, when an invalid locator was used to identify an element, the resulting behavior would be inconsistent in our bindings.

For example, let’s check the following code:

ArrayList<Class<? extends Exception>> expectedExceptions = new ArrayList<>();
 expectedExceptions.add(org.openqa.selenium.NoSuchElementException.class);
 expectedExceptions.add(org.openqa.selenium.StaleElementReferenceException.class);
 expectedExceptions.add(org.openqa.selenium.ElementNotInteractableException.class);
 expectedExceptions.add(org.openqa.selenium.InvalidElementStateException.class);
 
return new FluentWait<>(driver)
 .withTimeout(Duration.ofMillis(ELEMENT_IDENTIFICATION_TIMEOUT))
 .pollingEvery(Duration.ofMillis(ELEMENT_IDENTIFICATION_POLLING_DELAY))
 .ignoreAll(expectedExceptions)
 .until(nestedDriver -> {
 nestedDriver.findElement(By.xpath("invalid-xpath")).click;
 });

The expected result before this change would be that the driver waits until the timeout expires and then throw an InvalidSelectorException.

Exceptions on Selenium

InvalidSelectorException has changed