Skip to content

Core gesture handling module #72

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.

Sign up for GitHub

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

Jump to bottom
Closed
7 tasks done
jelbourn opened this issue Feb 11, 2016 · 4 comments
Closed
7 tasks done

Core gesture handling module #72

jelbourn opened this issue Feb 11, 2016 · 4 comments
Assignees
@kara
Labels
feature This issue represents a new feature or feature request rather than a bug or bug fix
Milestone
alpha.3

Comments

@jelbourn
Copy link
Member

jelbourn commented Feb 11, 2016 •
edited by kara
Loading

  • Research existing gesture libraries (polymer, hammer, etc.)
  • Propose approach
  • Define gesture vocabulary (swipe, pan, tap, drag, etc.)
  • Solidify path forward with hammer (alpha.2) (Tap fired twice in Chrome when using touch on Windows 8.1 / 10 hammerjs/hammer.js#917)
  • Support for devices with touch and mouse (alpha.3)
  • Create / modify Angular event plugin on top of module (alpha.3)
  • Ensure "drag" recognizer doesn't overwrite "pan"
@jelbourn jelbourn added the feature This issue represents a new feature or feature request rather than a bug or bug fix label Feb 11, 2016
@jelbourn jelbourn mentioned this issue Feb 11, 2016
Closed
@jelbourn jelbourn mentioned this issue Feb 24, 2016
Closed
@jelbourn jelbourn added this to the alpha.1 milestone Feb 25, 2016
@jelbourn jelbourn mentioned this issue Feb 27, 2016
Closed
@jelbourn
Copy link
Member Author

Research is done. Moving issue to next milestone for execution.

@jelbourn jelbourn modified the milestones: alpha.2, alpha.1 Mar 17, 2016
@jelbourn jelbourn modified the milestones: alpha.3, alpha.2 Apr 4, 2016
@jelbourn
Copy link
Member Author

jelbourn commented Apr 4, 2016

Moving to alpha.3 for completion of final parts

@jelbourn
Copy link
Member Author

@kara closing this as done.

@kara kara mentioned this issue May 1, 2016
Merged
@angular-automatic-lock-bot
Copy link

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

This action has been performed automatically by a bot.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 4, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees

@kara kara

Labels
feature This issue represents a new feature or feature request rather than a bug or bug fix
Projects
None yet
Milestone
alpha.3
Development

No branches or pull requests
2 participants
@jelbourn @kara