-
Notifications
You must be signed in to change notification settings - Fork 218
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
Crash at get_midpoint #364
Comments
Hi @makorne, are you using CSS or XPATH selector to find such button? |
Hi @masc-it
|
I had the same issue trying to click on a button
Looking in the code, the line @makorne pointed : I've checked with adding tab.wait_for_xpath(r#"//*[@id="bnp_btn_reject"]"#)?
.click()?; fixed the issue for me. Maybe we could change the code to something like this : let raw_quad = quad.quads.first().except("tried to get the midpoint of an element which is not visible"); to get a more helpfull error than
|
Hi!
Thank you for great crate!
After several successful click at the same button, something changed on page and:
thread 'main' panicked at 'called
Option::unwrap()on a
Nonevalue', /home/den/.cargo/git/checkouts/rust-headless-chrome-fd32a97e7a7fa8b4/60b775b/src/browser/tab/element/mod.rs:510:51
let raw_quad = quad.quads.first().unwrap();
<< this unwrapButtons div changed to
<div style="display: none;">
The text was updated successfully, but these errors were encountered: