Skip to content
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

core: increase Page.navigate timeout #6412

Merged
merged 2 commits into from
Oct 27, 2018

Conversation

connorjclark
Copy link
Collaborator

Fixes #6407

@paulirish paulirish merged commit 36ba984 into master Oct 27, 2018
@paulirish paulirish deleted the issue-6407-increase-page-navigate-timeout branch October 27, 2018 00:16
Copy link
Member

@brendankenny brendankenny left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

do we want a number (0? -1?) that disables the timeout? That feels slightly better than picking a number that's pretty good. In theory it's fine to ignore Page.navigate because the page load timeout will catch it regardless

@@ -840,6 +840,7 @@ class Driver {
// happen _after_ onload: https://crbug.com/768961
this.sendCommand('Page.enable');
this.sendCommand('Emulation.setScriptExecutionDisabled', {value: disableJS});
this.setNextProtocolTimeout(30 * 1000);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

These can 'race' and that's OK.

apparently not :)

Feels like we should await Page.enable and Emulation.setScriptExecutionDisabled (either they're short and it's no big deal or they're long and we need to account for them) but we can save that for another day.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants