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

Severe performance degradation from 2.0.2 to 2.0.3 #676

Closed
jperl opened this issue Oct 1, 2014 · 2 comments
Closed

Severe performance degradation from 2.0.2 to 2.0.3 #676

jperl opened this issue Oct 1, 2014 · 2 comments

Comments

@jperl
Copy link

jperl commented Oct 1, 2014

This example is using hammer.js@2.0.2 and this example is using hammer.js@2.0.3.

Here is the source code.

If you pull up a card (need touch emulation on) you will notice a severe performance degradation between the two versions, the only difference is the hammer version.

@runspired
Copy link
Contributor

Is this true for 2.0.4 as well?

@runspired
Copy link
Contributor

I'm closing this as out-of-date. @arschmitz it's likely this is still true though, at some point we should run through and make sure we don't have any args bindings that cause de-opts.

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