-
Notifications
You must be signed in to change notification settings - Fork 38
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
Equivalent of await page.waitForEvent("load");
#11
Comments
You don't have to wait explicitly because it will wait automatically after clicking.
|
|
The environment is manjaro Linux and I'm using playwright-rust with the chromium browser. |
If it hangs, please let me know with a code. |
Now I'm getting:
Even though I'm using |
Sorry, I forgot ignoreHTTPSErrors isn't a camelCase. 0.0.8 is ready. |
Thanks for the quick fix. #[tokio::main]
async fn main() -> Result<(), playwright::Error> {
let playwright = Playwright::initialize().await?;
playwright.prepare()?;
let chromium = playwright.chromium();
let browser = chromium
.launcher()
.headless(false)
.launch()
.await?;
let context = browser
.context_builder()
.ignore_https_errors(true)
.build()
.await?;
let page = context.new_page().await?;
page.goto_builder(LOGIN_URL).goto().await?; // here
Ok(())
} |
When I tried to reproduce the error, it was caused by parsing consolemessage, which was released at the same time. 0.0.9, how about this? |
Thanks for the quick fix. But now, at the same source line, it returns this error:
Any idea why? |
I tried it on a page with NET::ERR_CERT_AUTHORITY_INVALID, but unfortunately it did not reproduce. If you use env_logger and give me the output of |
Thanks, it works now (with v0.0.14). |
@octaltree Btw, is there a way to get the HTTP response from the latest request that was made? |
Would |
What's the equivalent of
await page.waitForEvent("load");
when using this crate? :)So that I can call it after e.g.
page.click_builder("#login-button").click().await?;
.When I try
page.expect_event(EventType::Load).await?;
it hangs here forever, even after the page loaded.The text was updated successfully, but these errors were encountered: