[Feature] Do not require waiting for navigation upon click
See original GitHub issueThe following pattern needs to go before we hit v1.0
const [response] = await Promise.all([
page.waitForNavigation(waitOptions),
page.click(selector, clickOptions),
]);
it should be simply
await page.click(selector, clickOptions);
Issue Analytics
- State:
- Created 4 years ago
- Reactions:4
- Comments:7 (7 by maintainers)
Top Results From Across the Web
Puppeteer wait page load after form submit - Stack Overflow
You can wait for navigation asynchronously to avoid getting null on redirection, await Promise.all([ page.click('button[type=submit]'), ...
Read more >Navigating & waiting - Checkly
In your scripts you can click on a link that triggers a navigation to a new page. You can use Puppeteer's page.waitForNavigation() method...
Read more >Avoiding hard waits in Playwright and Puppeteer
An auto-wait system failing once is no good reason for ditching the approach completely and adding explicit waits before every page load and ......
Read more >The 3-Click Rule for Navigation Is False
The 3-click rule is a persistent, unofficial heuristic that says that no page should take more than 3 clicks (or taps on a...
Read more >Browser automation actions reference - Power Automate
A physical click is required for cases where emulated clicks don't perform the intentional action on the element. As this option requires the ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This is now done, with
waitUntil
as @jperl was suggesting. I also pulled press intopage.press()
for convenience.And another question.
page.waitForNavigation()
waits for theload
event whereas forpage.click()
you chose the eventwaitForNavigation
- was there a reason? Reason I am asking is that in my case I could not replace the original post 1-to-1 with the new implementation.