New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
page.goto
is littered with races
#1218
Labels
Comments
This was referenced Oct 31, 2017
aslushnikov
added a commit
to aslushnikov/puppeteer
that referenced
this issue
Nov 10, 2017
This roll includes the following revisions: - crrev.com/515281 DevTools: fix crash on intercepting request that posts a blob - crrev.com/515368 DevTools: wait for navigation to be committed upon Page.navigate on the browser side. Fixes puppeteer#894, References puppeteer#1218
aslushnikov
added a commit
to aslushnikov/puppeteer
that referenced
this issue
Nov 10, 2017
This patch: - starts persisting lifecycle state for every frame - migrates NavigationWatcher to rely on these lifecycle events - refactors Page.goto to properly return navigation errors Fixes puppeteer#1218.
aslushnikov
added a commit
that referenced
this issue
Nov 10, 2017
This patch: - starts persisting lifecycle state for every frame - migrates NavigationWatcher to rely on these lifecycle events - refactors Page.goto to properly return navigation errors Fixes #1218.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Since the migration to lifecycle events (ce8a952), the
page.goto
,page.waitForNavigation
and other navigation methods are terribly flaky.We're fighting it upstream. This should be fixed before releasing next PPTR version.
The text was updated successfully, but these errors were encountered: