Does mixing Implicit and Explicit waits cause inconsistent timeout behavior?

Wait Strategy Conflict in Selenium WebDriver

Selenium WebDriver provides two primary mechanisms for handling asynchronous element loading: Implicit waits, which apply globally to the driver session, and Explicit waits (WebDriverWait), which target specific elements using ExpectedConditions.

While Explicit waits are generally preferred for precision, there is uncertainty regarding the internal interaction between these two mechanisms when active simultaneously. Specifically, the polling logic of a WebDriverWait may conflict with the global timeout of an Implicit wait, potentially leading to unpredictable delays that exceed the defined maximum timeout.

• Does the driver prioritize the Implicit wait timeout before the Explicit wait condition is evaluated?
• Which specific browser driver implementations exhibit the most variance when both wait types are configured?