Ripples behavior on touch-enabled devices doesn't match Android ripples behavior #7062
Assignees
Comments
devversion
added a commit
to devversion/material2
that referenced
this issue
Sep 25, 2017
* Ripples are now launched on touchstart for touch devices. Before they were just launched after the click happened. Fixes angular#7062
andrewseguin
pushed a commit
that referenced
this issue
Sep 29, 2017
* fix(ripple): handle touch events * Ripples are now launched on touchstart for touch devices. Before they were just launched after the click happened. Fixes #7062 * Address feedback
|
Thank you! |
devversion
added a commit
to devversion/material2
that referenced
this issue
Oct 20, 2017
* Now handles touch events properly. Fixes angular#7062
devversion
added a commit
to devversion/material2
that referenced
this issue
Oct 21, 2017
* Now handles touch events properly. Fixes angular#7062
jelbourn
pushed a commit
that referenced
this issue
Nov 18, 2017
* Now handles touch events properly. Fixes #7062
devversion
added a commit
to devversion/material2
that referenced
this issue
Nov 19, 2017
* Now handles touch events properly. Fixes angular#7062
tinayuangao
pushed a commit
that referenced
this issue
Nov 28, 2017
* Now handles touch events properly. Fixes #7062
tinayuangao
pushed a commit
to tinayuangao/material2
that referenced
this issue
Nov 29, 2017
* Now handles touch events properly. Fixes angular#7062
|
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. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug, feature request, or proposal:
Ripples behavior on touch-enabled devices doesn't match Android ripples behavior.
The ripple should happen during the touch, not after it.
What is the expected behavior?
What is the current behavior?
Please note that the ripple happened in the end, a bit of time after the button was clicked.
What are the steps to reproduce?
Go to https://material.angular.io/
What is the use-case or motivation for changing an existing behavior?
Follow Android design.
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
The latest ones for everything.
Is there anything else we should know?
The issue is also present when you enable touch-mode on Firefox for Windows. Untested on Chrome for Windows. The issue affects Chrome for Android and Firefox for Android, all latest versions.
Materialize CSS framework seems to have fixed this issue.
The text was updated successfully, but these errors were encountered: