You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The onDrawEnd callback is called initially, when the signaturepad is still empty. This makes it impossible to put some validation logic in this callback, because it will initially always be invalid (empty signature = invalid). It's not very friendly to display an error when the user hasn't done anything yet
Also, it's just not logical to call this callback initially when you look at the name. "onDrawEnd" indicates a segment has been drawn, but it hasn't. You can't have ended drawing a segment when nothing has been drawn.
So there you go. Two reason why this shouldn't happen in my opinion.
Signaturepad version I'm using: 2.4.0-1-g9c416df
Browser: Firefox 22 (although I don't think it's a browser issue)
The text was updated successfully, but these errors were encountered:
The onDrawEnd callback is called initially, when the signaturepad is still empty. This makes it impossible to put some validation logic in this callback, because it will initially always be invalid (empty signature = invalid). It's not very friendly to display an error when the user hasn't done anything yet
Also, it's just not logical to call this callback initially when you look at the name. "onDrawEnd" indicates a segment has been drawn, but it hasn't. You can't have ended drawing a segment when nothing has been drawn.
So there you go. Two reason why this shouldn't happen in my opinion.
Signaturepad version I'm using: 2.4.0-1-g9c416df
Browser: Firefox 22 (although I don't think it's a browser issue)
The text was updated successfully, but these errors were encountered: