You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
waitFor does not resolve but continues to wait until the set timeout is reached.
Expected behavior
Logically, once an element has been completely removed from the DOM, it no longer exists to be either "visible" or "hidden". In this case, waitFor State HIDDEN should recognize that the element no longer exists and resolve immediately, instead of waiting for a "hidden" state that can never occur.
Actual behavior
Playwright continues to wait until the set timeout is reached, leading to unnecessary delays in tests and potentially causing inaccurate failures.
Version
1.51.0
Steps to reproduce
Expected behavior
Logically, once an element has been completely removed from the DOM, it no longer exists to be either "visible" or "hidden". In this case, waitFor State HIDDEN should recognize that the element no longer exists and resolve immediately, instead of waiting for a "hidden" state that can never occur.
Actual behavior
Playwright continues to wait until the set timeout is reached, leading to unnecessary delays in tests and potentially causing inaccurate failures.
Additional context
No response
Environment
Playwright version: 1.51.0
Operating system: Windows 10
Programming language: Java
Browser: Chromium (Playwright's bundled version)
The text was updated successfully, but these errors were encountered: