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
I'm seeing the following after upgrading an older project's angular-gestures package to include the new recognizer check added via #41 . Specifically, the line where the direct function reference comparison is made. You can see in this debug output that there is a PanRecognizer defined (2nd entry) but it fails the comparison.
I'm including hammer.js and angular-gestures.js once, so I'm not sure what's creating this reference difference. Maybe making it more resilient by relying on the function name property instead makes sense though?
The text was updated successfully, but these errors were encountered:
I'm seeing the following after upgrading an older project's angular-gestures package to include the new recognizer check added via #41 . Specifically, the line where the direct function reference comparison is made. You can see in this debug output that there is a
PanRecognizer
defined (2nd entry) but it fails the comparison.I'm including
hammer.js
andangular-gestures.js
once, so I'm not sure what's creating this reference difference. Maybe making it more resilient by relying on the functionname
property instead makes sense though?The text was updated successfully, but these errors were encountered: