blocking-proxy
blocking-proxy copied to clipboard
Feature Request: Reduce waiting for Angular
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.
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