Execution context was destroyed, most likely because of a navigation - Error When Clicking Button

[Oskarowski]

Hello,
I'm encountering an issue when trying to use the ->click() method in Browsershot to dismiss the consent modal on music.youtube.com. My goal is to click the "Reject all" button and then capture the page’s HTML. However, when I run the following PHP code:

Here’s a PHP snippet of my code:

        $html = Browsershot::url($url)
            ->setOption('disableRedirects', false)
            ->setOption('headless', true)
            ->setOption('args', ['--no-sandbox'])
            ->setOption('disable-web-security', true)
            ->setOption('ignoreDefaultArgs', ['--enable-automation'])
            ->userAgent('Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/91.0.4472.124 Safari/537.36')
            ->click('button[aria-label="Reject all"]')
            ->setDelay(5000)
            ->bodyHtml();

puppeteer: ^24.4.0
spatie/browsershot: ^5.0
node: v22.7.0

The page navigates after clicking the button, which destroys the execution context before the HTML is captured.

The command ""C:\Program Files\nodejs\node.EXE" C:\Project\vendor\spatie\browsershot\src/../bin/browser.cjs "{""url"":""https:\/\/music.youtube.com\/search?q=Fight+Back+NEFFEX&hl=en"",""action"":""content"",""options"":{""args"":[""--no-sandbox""],""viewport"":{""width"":800,""height"":600},""disableRedirects"":false,""headless"":true,""disable-web-security"":true,""ignoreDefaultArgs"":[""--enable-automation""],""userAgent"":""Mozilla\/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit\/537.36 (KHTML, like Gecko) Chrome\/91.0.4472.124 Safari\/537.36"",""clicks"":[{""selector"":""button[aria-label=\""Reject all\""]"",""button"":""left"",""clickCount"":1,""delay"":0}]}}"" failed.

Exit Code: 1(General error)

Working directory: C:\Project\public

Output:
================


Error Output:
================
Error: Execution context was destroyed, most likely because of a navigation.
    at rewriteError (C:\Project\node_modules\puppeteer-core\lib\cjs\puppeteer\cdp\ExecutionContext.js:455:15)
    at async #evaluate (C:\Project\node_modules\puppeteer-core\lib\cjs\puppeteer\cdp\ExecutionContext.js:388:60)
    at async ExecutionContext.evaluate (C:\Project\node_modules\puppeteer-core\lib\cjs\puppeteer\cdp\ExecutionContext.js:277:16)
    at async IsolatedWorld.evaluate (C:\Project\node_modules\puppeteer-core\lib\cjs\puppeteer\cdp\IsolatedWorld.js:100:16)
    at async CdpFrame.evaluate (C:\Project\node_modules\puppeteer-core\lib\cjs\puppeteer\api\Frame.js:348:20)

For comparison, in a JavaScript environment I handled this by explicitly waiting for the selector and navigation:

await page.waitForSelector('button[aria-label="Reject all"]', { timeout: 5000 });
await page.click('button[aria-label="Reject all"]');
await page.waitForNavigation({ waitUntil: 'networkidle2' });

Is there a way to achieve similar behavior waitForNavigation in Browsershot? For example, could we delay the HTML capture until after the navigation is complete, or is there another workaround to ensure that the page's state is stable before calling bodyHtml()?

Any help or guidance would be greatly appreciated. Thanks for your time and for maintaining Browsershot!