-
Notifications
You must be signed in to change notification settings - Fork 9.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
Material send icon inconsistent/incorrect #1668
Comments
As you have noticed, the old Material Icons do not have the same kind of updates and maintenance that Material Symbols is getting. Is switching to the newer icon set an option? |
For Android (Compose) only the material icons seems to be readily available as a library and I can't seem to find anything on the Material Symbols usage. Of course it'd be possible to manually add the symbols as a "custom" icon in the app and use that instead, but that's not really a road I want to go down. |
I am wondering if it might be in the Compose Material 3 library, that being the latest? https://developer.android.com/jetpack/androidx/releases/compose-material3 |
The Material 3 library unfortunately uses the old icons.
I'm don't know about all the differences between the icons and symbols, or why the relatively new material (3) library uses the old icons, but it looks like these icons simply aren't available yet as part of the material libraries. I've created a feature request for the symbols to be added, but I was hoping the icons could be fixed anyways since it simply seemed to render incorrectly (and the fixed version already exists for the symbols). |
The material send icons seems to be rendered incorrectly for both "send" and "cancel_schedule_send". The paper plane for these icons is different from the plane used in the other send icons and in the material symbols (new) set.
When comparing the "schedule_send" icon and the "cancel_schedule_send" the difference becomes quite clear.
In the Material Symbols (new) set, the icons are displayed consistently:
The text was updated successfully, but these errors were encountered: