-
Notifications
You must be signed in to change notification settings - Fork 4.4k
chore: move timeout handling to the client #35988
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
Conversation
This comment has been minimized.
This comment has been minimized.
Test results for "tests 2"12 failed 145 flaky239469 passed, 9341 skipped Merge workflow run. |
@@ -1611,7 +1590,7 @@ Page: | |||
goBack: | |||
title: Go back | |||
parameters: | |||
timeout: number? | |||
timeout: number |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm a little worried that it's very easy to break in the ports without noticing. Maybe we can store per-client default timeouts on the server end?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'll try to roll into languages and see how it goes.
packages/playwright-core/src/server/dispatchers/elementHandlerDispatcher.ts
Show resolved
Hide resolved
2844b4b
to
34b5bb0
Compare
This comment has been minimized.
This comment has been minimized.
34b5bb0
to
ab22d59
Compare
Test results for "tests 1"3 failed 7 flaky39229 passed, 804 skipped Merge workflow run. |
References #35987.