-

[webbseo]

[github-actions]

This issue was not reproducible. Please check that your example runs locally and the following:

• Ensure the script does not rely on dependencies outside of puppeteer and puppeteer-core.
• Ensure the error string is just the error message.

  • Bad:

    Error: something went wrong
      at Object.<anonymous> (/Users/username/repository/script.js:2:1)
      at Module._compile (node:internal/modules/cjs/loader:1159:14)
      at Module._extensions..js (node:internal/modules/cjs/loader:1213:10)
      at Module.load (node:internal/modules/cjs/loader:1037:32)
      at Module._load (node:internal/modules/cjs/loader:878:12)
      at Function.executeUserEntryPoint [as runMain] (node:internal/modules/run_main:81:12)
      at node:internal/main/run_main_module:23:47

  • Good: Error: something went wrong.

• Ensure your configuration file (if applicable) is valid.
• If the issue is flaky (does not reproduce all the time), make sure 'Flaky' is checked.
• If the issue is not expected to error, make sure to write 'no error'.

Once the above checks are satisfied, please edit your issue with the changes and we will
try to reproduce the bug again.

---

Analyzer run

[webbseo]

It worked before but now it doesn't even after downgrading both puppeteer and firefox.

[webbseo]

tried switching frames and debugging . WaitForSelector doesn't work neither.
Seems its overall puppeteer page recognition and not specific to page.goto.

[Lightning00Blade]

Hello @webbseo this seems to be a Firefox issue, something is preventing the browser from proceeding.
I can see this is only happening for Google Search only. Trying it with example.com works as expected

cc @whimboo I can see a banner showing for Searching got simpler, maybe that is the problem?

[whimboo]

No, this is a dupe of issue #6940.