Implement subset of improved interaction response guidelines for ripple #190
Assignees
Labels
Comments
cristobalchao
pushed a commit
that referenced
this issue
Feb 19, 2017
…lines for ripple Resolves #190
cristobalchao
pushed a commit
that referenced
this issue
Feb 24, 2017
…lines for ripple Resolves #190
cristobalchao
pushed a commit
that referenced
this issue
Feb 28, 2017
…lines for ripple Resolves #190
cristobalchao
pushed a commit
that referenced
this issue
Feb 28, 2017
…lines for ripple Resolves #190
cristobalchao
pushed a commit
that referenced
this issue
Feb 28, 2017
…lines for ripple Resolves #190
cristobalchao
pushed a commit
that referenced
this issue
Mar 1, 2017
…lines for ripple Resolves #190
cristobalchao
pushed a commit
that referenced
this issue
Mar 2, 2017
…lines for ripple Resolves #190
cristobalchao
pushed a commit
that referenced
this issue
Mar 8, 2017
…lines for ripple Resolves #190
cristobalchao
pushed a commit
that referenced
this issue
Mar 8, 2017
…lines for ripple Resolves #190
cristobalchao
pushed a commit
that referenced
this issue
Mar 8, 2017
…lines for ripple Resolves #190
cristobalchao
pushed a commit
that referenced
this issue
Mar 10, 2017
…lines for ripple Resolves #190
cristobalchao
pushed a commit
that referenced
this issue
Mar 14, 2017
…lines for ripple Resolves #190
traviskaufman
pushed a commit
that referenced
this issue
Mar 14, 2017
…lines for ripple Resolves #190
cristobalchao
pushed a commit
that referenced
this issue
Mar 14, 2017
…lines for ripple Resolves #190
traviskaufman
added a commit
that referenced
this issue
Mar 21, 2017
…lines for ripple - Implement UX changes for "tap" + "tap and hold" interactions - Remove all references of "bounded" vs. "unbounded" from activation/deactivation code Resolves #190
traviskaufman
added a commit
that referenced
this issue
Mar 21, 2017
…lines for ripple - Implement UX changes for "tap" + "tap and hold" interactions - Remove all references of "bounded" vs. "unbounded" from activation/deactivation code Resolves #190
traviskaufman
added a commit
that referenced
this issue
Mar 21, 2017
…lines for ripple - Implement UX changes for "tap" + "tap and hold" interactions - Remove all references of "bounded" vs. "unbounded" from activation/deactivation code Resolves #190
traviskaufman
added a commit
that referenced
this issue
Mar 24, 2017
…lines for ripple - Implement UX changes for "tap" + "tap and hold" interactions - Remove all references of "bounded" vs. "unbounded" from activation/deactivation code Resolves #190
traviskaufman
added a commit
that referenced
this issue
Mar 28, 2017
…lines for ripple Background === When the ripple was originally designed from a motion perspective, bounded and unbounded activation/deactivation used two different animation styles, distinct from one another. The UX updates to the ripple remove this distinction of bounded vs. unbounded solely with regard to how the ripple animates in and out. There is still a distinction between bounded vs. unbounded, but we no longer have to account for this when animating the ripple. Thus, there are no API changes; only UX changes. Changes === - Implement UX changes for "tap" + "tap and hold" interactions - Remove all references of "bounded" vs. "unbounded" from activation/deactivation code Resolves #190
traviskaufman
added a commit
that referenced
this issue
Mar 28, 2017
…lines for ripple Background === When the ripple was originally designed from a motion perspective, bounded and unbounded activation/deactivation used two different animation styles, distinct from one another. The UX updates to the ripple remove this distinction of bounded vs. unbounded solely with regard to how the ripple animates in and out. There is still a distinction between bounded vs. unbounded, but we no longer have to account for this when animating the ripple. Thus, there are no API changes; only UX changes. Changes === - Implement UX changes for "tap" + "tap and hold" interactions - Remove all references of "bounded" vs. "unbounded" from activation/deactivation code Resolves #190
traviskaufman
added a commit
that referenced
this issue
Mar 28, 2017
…lines (#419) Background === When the ripple was originally designed from a motion perspective, bounded and unbounded activation/deactivation used two different animation styles, distinct from one another. The UX updates to the ripple remove this distinction of bounded vs. unbounded solely with regard to how the ripple animates in and out. There is still a distinction between bounded vs. unbounded, but we no longer have to account for this when animating the ripple. Thus, there are no API changes; only UX changes. Changes === - Implement UX changes for "tap" + "tap and hold" interactions - Remove all references of "bounded" vs. "unbounded" from activation/deactivation code Resolves #190
pgbross
pushed a commit
to pgbross/material-components-web
that referenced
this issue
Mar 29, 2017
…lines (material-components#419) Background === When the ripple was originally designed from a motion perspective, bounded and unbounded activation/deactivation used two different animation styles, distinct from one another. The UX updates to the ripple remove this distinction of bounded vs. unbounded solely with regard to how the ripple animates in and out. There is still a distinction between bounded vs. unbounded, but we no longer have to account for this when animating the ripple. Thus, there are no API changes; only UX changes. Changes === - Implement UX changes for "tap" + "tap and hold" interactions - Remove all references of "bounded" vs. "unbounded" from activation/deactivation code Resolves material-components#190
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The rest of the improved interaction response guidelines will be covered in separate stories.
The text was updated successfully, but these errors were encountered: