Can Stand

Handle it in another gorountine ```go func handleResponse(res playwright.Response) { go func() { ... }() } } ``` or refer to [this](https://github.com/playwright-community/playwright-go/blob/9a40c60dfee0b1e3b6ec54584bffbc1b9e0a375b/tests/browser_context_test.go#L531)

Run driver with params: https://github.com/playwright-community/playwright-go/blob/6b672dbd24505206feca7c2b660da8d616c6393f/tests/remote_server_test.go#L23 https://github.com/microsoft/playwright/blob/9fcf60464d983b70b3cafea3e230e4e6e4f92c15/packages/playwright-core/src/cli/program.ts#L263

Please log if there is an error when closing BrowserContext. ```go defer func() { err := context.Close() if err != nil { log.Printf("Failed to close browser context: %v", err) }...

And https://github.com/microsoft/playwright/issues/34230

Hi @Nialito, sorry I don't have time to test. Since the screenshot shows the increase in node memory, I suggest you write a js script with the same function and...

> The difference between the Locator and ElementHandle is that the latter points to a particular element, while Locator captures the logic of how to retrieve that element. (https://playwright.dev/docs/release-notes#-new-locators-api) Maybe...

Sorry for the delay. I haven't dug into the details of the upstream implementation, but I don't think Locator caches the ElementHandle.

Hi @mxschmitt , Playwright throws an error and exits on certificate mismatch. The difference with the playwright-python test is that the TLS server uses the go standard option `tls.RequireAndVerifyClientCert`. Pls...

@mxschmitt after disabling http2, the Windows tests have a [similar error](https://github.com/playwright-community/playwright-go/actions/runs/10521755525/job/29153867738?pr=480#step:7:154), but only on go 1.22 and lower.

You don't need `ExcutablePath`, specify the `Channel` and let Playwright find it automatically.