-
Notifications
You must be signed in to change notification settings - Fork 262
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
isPointInPath sometimes returns wrong value #28
Comments
Thanks for the report! Conceptually this makes sense since we are tinkering with the drawing dimensions behind the scenes. In reviewing the documentation for isPointInPath, it looks like it can sometimes take arguments that are not just x and y. Do you happen to be using any of those arguments? This fix might entail overriding The quickest path to a fix would likely be writing a few simplified failing tests that emulate your use case here. |
Hi, Thank you for your quick reply. As for your question about the fillRule or path arguments, I did not use any of them. Unfortunately, I have never written tests and don't know how to use them. Here is a simplified example of what I'm trying to achieve (I use d3.js): HTML:
JS:
Thank you for your help |
Hi
Thank you for your great polyfill.
I do have a small problem with it: isPointInPath sometimes returns a wrong value - true instead of false, and false instead of true.
My application draws a dial which can be turned around. After adding your script, the dial sometimes doesn't turn, even though the touch point is on it.
Do you have an idea what could be the cause of this? I can give more details if needed, just don't want to overwhelm straight out.
Thank you
The text was updated successfully, but these errors were encountered: