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

Add "element click intercepted" error #108

Open
eternal-sorrow opened this issue Dec 15, 2020 · 2 comments
Open

Add "element click intercepted" error #108

eternal-sorrow opened this issue Dec 15, 2020 · 2 comments

Comments

@eternal-sorrow
Copy link

eternal-sorrow commented Dec 15, 2020

As shown here, there is a "element click intercepted" error possible, but there is no ElementClickIntercepted in arsenic.errors, so this error is raised as UnknownArsenicError. This is as easy as adding ElementClickIntercepted = create("element click intercepted", 35) to errors.py. Or with another value for code, whatever this argument mean.

As a workaround, I added this line to my own module, so that I was able to catch this exact error.

@dimaqq
Copy link
Contributor

dimaqq commented Dec 16, 2020

PR is most welcome!
P.S. how to trigger this error? How to test the change?

@eternal-sorrow
Copy link
Author

how to trigger this error?

Element Click command could not be completed because the element receiving the events is obscuring the element that was requested clicked.

Reference

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

No branches or pull requests

2 participants