-
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
The ripple causes strange margin - reproduced #14981
Comments
Hi @kfrankiewicz, thanks for your issue! The Most of the time ripples can be launched safely by creating an absolute overlapping transparent container that acts as the ripple container and does not affect the parent elements. this can be seen in the Also, I commented on your proposal #14982. Let's track this issue for compatibility with the We can also have an issue for the tab-group compatibility, but we need to figure out if we actually want to guarantee that every Material component is working fine with additional custom ripples. Developers should be always able to properly use the `matRipple´ directive as long as the surrounded elements are properly handled. |
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. |
Related issues:
#10898
#12210
The ripple creates strange margins, when position: relative is added to the children divs in the global CSS. The recent angular versions. In my case I used mat-tab-group with the ripple.
It causes this problem:
https://stackblitz.com/edit/angular-m5y3yx?file=src%2Fapp%2Fapp.component.html
It seems the position: absolute (or whatever it is) from the ripple is overwritten by the global position.
The ripple works well when I add this globally:
The text was updated successfully, but these errors were encountered: