-
Notifications
You must be signed in to change notification settings - Fork 6.7k
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
disableRipple on list item leaves ripple class with overflow:hidden side effect #4156
Comments
Agreed- there shouldn't be a |
I don't think it will be possible to drop the When the ripples are disabled, removing |
Why not have the ripple container be a child of the list item that is |
That would be the easiest solution. I did something similar in Material 1 with the underlying button. I'll play with it. |
I think that solution would solve #4275 too (assuming that 4275's issue is stacking context related) |
I don't really think that those issues relate together. Issue #4275 is about |
Ahh ok. I initially read Jeremy's answer as proposing that the |
@willshowell Yeah exactly. Letting the |
* Removes the `overflow: hidden` on the list-items by moving the ripples into a child element that overlays the content. Fixes angular#4156
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:
Bug
What is the expected behavior?
When using
disableRipple
on a list item,.mat-ripple
class should be removed.What is the current behavior?
.mat-ripple
class remains on themat-list-item-content
.What are the steps to reproduce?
https://plnkr.co/edit/lO8Eudx4GFgevN4XAy3n?p=preview
What is the use-case or motivation for changing an existing behavior?
Justification here. The
.mat-ripple
class addsoverflow: hidden
.It may be entirely valid that list items should always have
overflow: hidden
on their content, but that should be done explicitly and not through a side effect of the ripple class.The text was updated successfully, but these errors were encountered: