generated from Xetera/typescript-starter
-
Notifications
You must be signed in to change notification settings - Fork 125
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
How to avoid sometimes clicking on adjacent elements with cursor.click? #120
Comments
Do you have a reproducible test page for this? |
the problem is relevant |
Yeah it happens actually, I will speculate it is because of the element's box, we need to make a test page for it for sure, for me it happens on complicated websites and pretty rarely so I wasn't able to catch it yet. |
There are often sticky components or small windows that cover the element to click. may you expose a parameter to specify the click position within the element?I found an option there: paddingPercentage, it works for me. |
Yep, use /**
* Percentage of padding to be added inside the element when determining the target point.
* Example:
* - `0` = may be anywhere within the element.
* - `100` = will always be center of element.
* @default 0
*/
readonly paddingPercentage?: number |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
I speculate that perhaps the clicking occurs before the mouse movement has completely stopped, but even when I tried adding a delay before the click, the issue still occurred.
The text was updated successfully, but these errors were encountered: