-
Notifications
You must be signed in to change notification settings - Fork 194
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Better way to ensure DOM is settled #217
Comments
Eventually I'd like to deprecate Playwright and rely on Computer Use; so a "native" solution would be cool. We could always start with PW and then eventually deprecate. |
Understood. I will pick it up shortly and implement it without Playwright Asking about your vision—are you aiming for Shortest to eventually become the "next-gen Playwright"? |
Yep! "Playwright can automate browser tasks in Chromium, Firefox, and WebKit with a single API." Eventually computer use will be able to do all of this, and there won't be a need for playwright. I think we should bet on this! |
Agree! |
What
Get rid of
setTimeout
and use Playwright API insteadWhy
Currently, we use timeouts, wait one second before performing any actions on a page:
new Promise((resolve) => setTimeout(resolve, ms));
This is ineffective for several reasons:
The text was updated successfully, but these errors were encountered: