| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
|
I don't quite understand why server-side code would lead to a timeout, but client-side check sounds good to me. |
Sorry, something went wrong.
|
The server-side check is in a retry condition, and we don't abort the retry when it occurs. Client-side is better anyways because it throws the platform-standard exceptions. |
Sorry, something went wrong.
| Back | FazBrowse Home | New Git URL |
Closes microsoft/playwright#38450. We were only checking file existence on the server (https://github.com/microsoft/playwright/blob/f9e039408b70ab27b5107de3863343236d8835ae/packages/playwright-core/src/server/dom.ts#L655-L657), but didn't surface the error, so it showed up as a timeout. In Node.js, we check file existence on the client (https://github.com/microsoft/playwright/blob/f9e039408b70ab27b5107de3863343236d8835ae/packages/playwright-core/src/client/elementHandle.ts#L263), mirroring this behaviour to Python.