Alex Rudenko
Alex Rudenko
Another safe way is to use page.waitForSelector or page.locator API: ``` const element = await page.waitForSelector('.foo'); const element = await page.locator('.foo').waitHandle(); ```
I have been thinking about this issue, and I do not see a good solution. For test scenarios, I'd recommend waiting for network idle events. For automation, perhaps re-trying on...
@Vasile-Peste you can retry the operation if you catch the Execution context was destroyed error.
@Lightning00Blade PTAL
To clarify, CDP explicitly serialized to JSON while BiDi serialization aims at maintaining the actual types and TypedArrays are not supported. You can use ``` const foo = await page.evaluate(()...
The fix will be available once Puppeteer ships Chrome 127.
@Riyazul555 please sign the CLA so that the CLA check passes
@Riyazul555 you can follow the instructions from the check posted above https://github.com/puppeteer/puppeteer/pull/12687/checks?check_run_id=26852656282
I think it still not detected
Hey, it sounds like it is an issue with Chrome and not Puppeteer that is only used to start the browser? Did you try using the latest Puppeteer and the...