-
Notifications
You must be signed in to change notification settings - Fork 143
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
FAB artifact on click when using com.google.android.material:material:1.1.0 #146
Comments
Please provide all the information required when you open a bug report:
|
Library version: 3.1.1 |
For better Test change Color overlay to black ! |
I can reproduce the issue using I can't do anything about this since it's a bug of the google material library. My advice is to use the version 1.2.0-alpha04 if you can or don't use the material library at all. |
i use material:1.2.0-alpha04 But the problem was not solved |
if google material library has bug Why this is ok ? i use both lib FloatingActionButtonSpeedDial and floating action button in the my project but only FloatingActionButtonSpeedDial has bug ! |
Don't use paddingCompat can fix this. I am using this library in my app Pure Writer, and got the same bug on Android 5.1.1, I finally fixed it by using real margins and no clips. |
This bug can be reproduced on Android 5.1.1 emulator/AOSP ROM. |
Yes, it's the cause. |
Items have the same bug :| |
@leinardi help :( |
you can try this:
|
@BrightVan |
|
I have provided the exact solution:
Remove FAB I am sorry, I made a lot of local changes to this library, so I can’t create a PR or share related code directly. But I can take a screenshot for the source code: (You can see my app for the performance result https://play.google.com/store/apps/details?id=com.drakeet.purewriter) |
This issue has been automatically marked as stale because it has not had activity in the last 60 days. |
Hi this library is having a problem at Ripple
This is a problem when we click on the fab button
See the picture below to find out
The text was updated successfully, but these errors were encountered: