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

fix(gestures): custom recognizers should not inherit twice. #902

Merged
merged 2 commits into from Jul 25, 2016

Conversation

devversion
Copy link
Member

  • HammerJS does not allow custom recognizers to use a default recognizer twice globally.
    This means that we can't create a drag and slide recognizer, which depends for all on one default recognizers.

As discussed with @kara this is another approach for fixing that gesture issues.

@googlebot googlebot added cla: yes PR author has agreed to Google's Contributor License Agreement labels Jul 22, 2016
@kara
Copy link
Contributor

kara commented Jul 22, 2016

@devversion A few notes:

  • Swipe still appears to be broken. Can you fix?
  • Can you add slide to the gestures demo test page?
  • Rebase now needed. Thanks!

* HammerJS does not allow custom recognizers to use a default recognizer twice globally.
  This means that we can't create a `drag` and `slide` recognizer, which depends for all on one default recognizers.
@devversion devversion force-pushed the fix/gestures-twice-inheritances branch from b4c073f to da5f6f5 Compare July 22, 2016 20:38
@devversion
Copy link
Member Author

@kara Done!

@kara
Copy link
Contributor

kara commented Jul 22, 2016

Thanks for updating! LGTM

@kara kara added pr: lgtm action: merge The PR is ready for merge by the caretaker and removed pr: needs cleanup / tests action: merge The PR is ready for merge by the caretaker labels Jul 22, 2016
@hansl hansl merged commit c68efbd into angular:master Jul 25, 2016
@devversion devversion deleted the fix/gestures-twice-inheritances branch July 26, 2016 04:51
@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 6, 2019
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
action: merge The PR is ready for merge by the caretaker cla: yes PR author has agreed to Google's Contributor License Agreement
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants