[🐛 Bug]: Webdriver Wait is not working in selenium C# and this issue exists for both implicit and explicit wait time.

[sathisharumugamag]

What happened?

I'm currently encountering a potential issue with our existing selenium C# framework. For some reason, the wait time isn't functioning correctly in the Selenium C# environment. As I check with Java it is functioning properly but C# is failing with both implicit and explicit waits.

Relying on Thread.Sleep to create a global wait isn't the best practice for automation scripting, as it can lead to longer execution times.

Please take a look at the attached video; based on the wait time, the script should pause at that line instead of moving immediately. Here the wait time was 8333333 minutes.

Video Recording:
https://drive.google.com/file/d/1zY8n4H98DzIDiTCtoR_08tHJ9E3szeVk/view?usp=sharing

Automation Tech Stack:
Language : C#
Selenium WebDriver :
Selenium Support:
Selenium wait :

How can we reproduce the issue?

Here is the sample of implicit and explicit wait 

public void ImplicitWait()
{
driver.Manage().Timeouts().ImplicitWait = TimeSpan.FromSeconds(5000);
}

public void ExplicitWait()
{
     WebDriverWait wait = new WebDriverWait(driver, TimeSpan.FromSeconds(5000));
     wait.Until(ExpectedConditions.ElementIsVisible(By.Id(ID)));
}

Relevant log output

Selenium Wait is not working hence the driver immediately looks for my element and it is not enabled on the web page, so it is throwing this error. 

Message: 
OpenQA.Selenium.ElementNotInteractableException : element not interactable
  (Session info: MicrosoftEdge=133.0.3065.92)

  Stack Trace: 
WebDriver.UnpackAndThrowOnError(Response errorResponse, String commandToExecute)
WebDriver.Execute(String driverCommandToExecute, Dictionary`2 parameters)
WebDriver.InternalExecute(String driverCommandToExecute, Dictionary`2 parameters)
WebElement.Execute(String commandToExecute, Dictionary`2 parameters)
WebElement.SendKeys(String text)

Operating System

Windows 10

Selenium version

C# 4.29.0

What are the browser(s) and version(s) where you see this issue?

IE edge, Chrome, Firefox

What are the browser driver(s) and version(s) where you see this issue?

MicrosoftEdge=133.0.3065.92, chrome=133.0.6943.142

Are you using Selenium Grid?

No

[github-actions]

@sathisharumugamag, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

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!

[Piedone]

Maybe related? https://groups.google.com/g/selenium-users/c/vfG6A6XVkA0 But I only started to see this with Chrome 134.0.6998.35.

[RenderMichael]

By default, WebDriverWait will retry on any exception extending NotFoundException, such as ElementNotFounfException, AlertNotFoundException, and WindowNotFoundException. Any other exception is not considered an "ignored exception" and will stop the execution. Notable exceptions thrown include ElementNotInteractableException and StaleElementReferenceException. Hitting either of these is arguably a bug in the logic, but there can be valid use cases to retry on those exceptions.

To do so, simply add the desired exception type to the set of ignored exceptions, like so:

WebDriverWait wait = new WebDriverWait(driver, TimeSpan.FromSeconds(5000));
wait.IgnoreExceptionTypes(typeof(ElementNotInteractableException));
wait.Until(ExpectedConditions.ElementIsVisible(By.Id(ID)));

As this is intended behavior, I will be closing this issue. Feel free to ask any follow-up questions though. Thank you.

[selenium-ci]

Hi, @sathisharumugamag.

This is related to code in the Support packages. The support packages contain example code that
many users find helpful, but they do not necessarily represent the best practices for using Selenium,
and the Selenium team is not prioritizing work on them right now.
This doesn't mean that we won't ever work on them, but it is not on our roadmap as we push to release Selenium 5.

We actively encourage people to create their own wrapper and helper code that makes sense for them.
If you have any questions, please contact us

[RenderMichael]

Looking through the associated conversation in the Google group, this does not appear to be a Selenium issue. Either way, this issue can be closed, and the bug should be reported to Chrome.

[github-actions]

This issue has been automatically locked since there has not been any recent activity since it was closed. Please open a new issue for related bugs.