-
Notifications
You must be signed in to change notification settings - Fork 6.8k
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
Ripple on mat-row breaks cells in 6.0 version #11165
Comments
Your explanation has unclear english but I believe I'm having the same issue (using mat-table with flex model). The problem is that the way ripple works is to add a The new css for version 6 contains the following to add padding to the left and right of a table.
So as soon as I don't have a hacky solution - choosing to just ignore it for now and wait for a proper fix. |
gross !important, hopefully this gets fixed sooner than later |
Fixes extra decorative elements like badges or ripples throwing off the alignment in tables. Fixes angular#11165.
Fixes extra decorative elements like badges or ripples throwing off the alignment in tables. Fixes #11165.
Fixes extra decorative elements like badges or ripples throwing off the alignment in tables. Fixes #11165.
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?
Ripple on mat-row
What is the current behavior?
Ripple effect last cells padding in material table and breaks all row
What are the steps to reproduce?
https://stackblitz.com/edit/angular-material2-issue-gd2jqa
What is the use-case or motivation for changing an existing behavior?
If it is problem in new ripple logic it may affects not only row component of material controls
Which versions of Angular, Material, OS, TypeScript, browsers are affected?
material 6.0
Is there anything else we should know?
All works fine in previous versions
The text was updated successfully, but these errors were encountered: