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
{{ message }}
This repository has been archived by the owner on Dec 29, 2022. It is now read-only.
The AngularWaitBarrier currently waits for Angular before each command. This is overkill. It could track whether the app is "dirty" or not by remembering if it's run waitForAngular since the most recent command that could have triggered Angular's change detection. This would include click, send keys, mouse actions, alert actions, and potentially executeScript calls.
The text was updated successfully, but these errors were encountered:
But Angular can get changed even without triggers from user interactions, but also from server side pushes. We can't be sure that there was no server pushes to client
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
The AngularWaitBarrier currently waits for Angular before each command. This is overkill. It could track whether the app is "dirty" or not by remembering if it's run waitForAngular since the most recent command that could have triggered Angular's change detection. This would include click, send keys, mouse actions, alert actions, and potentially executeScript calls.
The text was updated successfully, but these errors were encountered: