-
-
Notifications
You must be signed in to change notification settings - Fork 137
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
Add ability to specify options for browser.goto #41
Comments
+1 there's an SSL error (e.g. in case of self-signed certificates). NOTE page.goto either throws an error or returns a main resource response. The only exceptions are navigation to about:blank or navigation to the same URL with a different hash, which would succeed and return null. NOTE Headless mode doesn't support navigation to a PDF document. See the upstream issue. Shortcut for page.mainFrame().goto(url, options) |
In fact it's the major difference between the two. Puppeteer will return control right after it gets response from Chrome that goto command accepted, but Ferrum waits until the page is loaded. If there's JS on the page or some async rendering nothing will help because there's no way to realise that async rendering is done. So if you want to wait that there are no pending network connections I suggest using |
Currently it's not possible to specify options in
browser.goto
, but some options are necessary, for examplewait_until
as in puppeteerThe text was updated successfully, but these errors were encountered: