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
mdList - Add swipe animation for items #4016
Comments
This is also described in https://material.io/guidelines/components/lists-controls.html#lists-controls-types-of-list-controls as |
+1 |
1 similar comment
+1 |
Using hammerJS and angular 4.2 animations this should be fairly easy. But should it really be part of core? Supporting touch is optional and on desktop it does nothing but bloat the framework :/ |
That's true. Where i'm currently consulting, we did a custom implementation using Hammerjs. That was fairly easy. It would be awesome to have something like this in a touch module, in order to reduce bloat 😊 |
@mackelito , @LarsVonQualen would have an example in codepen, how to do using the hammerjs |
@LarsVonQualen could you provide an example code? |
As of Angular v9, we've decided to step back from the aspiration of adding gestures directly to the components, instead having the component library be agnostic to geature recognition. That said, we do still want to add documentation that explains how to go about adding gestures to the components. |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Bug, feature request, or proposal:
feature request
What is the expected behavior?
Allow list-items to be swiped left/right to reveal additional actions on the item. Draging the item further should activate the outermost action.
What is the use-case or motivation for changing an existing behavior?
Many big applications already use this (gmail, iOS Mail, ...) and it is a rather common/already trained user behaviour.
Implemented in:
Planned in Angular Material 1 (angular/material#1890)
The text was updated successfully, but these errors were encountered: