-
Notifications
You must be signed in to change notification settings - Fork 9.4k
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(fr): user triggered navigations #13496
Conversation
session.setNextProtocolTimeout(Infinity); | ||
waitForPageNavigateCmd = session.sendCommand('Page.navigate', {url: requestor}); | ||
} else { | ||
waitForPageNavigateCmd = requestor(); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It could be useful to make a new status logging step here, and keep the original for this method the same.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We will have to replace the URL in the original log message with something for user controlled navigations. I think that would make a log statement here redundant.
I'm gonna start working on test cases, but this is ready for review otherwise. |
…hthouse into fr-navigation-requestor
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
just add some docs about best practices for requestor function and LGTM!
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
love it
Welcome to the future 😎 |
Doc
Interested in any feedback on the callback implementation.
Some details not mentioned in design doc:
requestedUrl
in a lot of places because we don't have prior knowledge of the URL with a callback function.Related
#13375
#11313