-
Notifications
You must be signed in to change notification settings - Fork 6.8k
feature: extended FAB (Floating Action Button) #12246
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
Comments
This would be a great addition. Really, anything introduced in Material Design 2.0 would be amazing if added. |
That's a great addition. |
Workaround that looks pretty close:
|
Is this feature not coming? |
Any updates on this? Are there any particular challenges with this issue? |
Workaround works well, but I would love to see this supported by the |
any information about #15645 @josephperrott , @jelbourn ? |
@JWess in order for your workaround to work in IE11, you need to change |
This is supported in the MDC version of the FAB which will become the default eventually. If you want to start using it now, you can import the <button mat-fab extended>
<mat-icon>check</mat-icon>
Search
</button> |
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:
Feature request
What is the expected behavior?
To have the Extended FAB (Floating Action Button) as a Material component, as designed in the Google Material Design.
See for more examples the Google Material Design documentation.
What is the current behavior?
There's currently no (extended) FAB to use when you can't explain an action with only an icon (as the FAB itself is designed for).
What is the use-case or motivation for changing an existing behavior?
To follow the Google Material Design and its components. There's now no component to provide the kind of interaction a FAB has plus a text label.
Is there anything else we should know?
It was already mentioned before in #11534, but it was closed due to not following the issue template.
The text was updated successfully, but these errors were encountered: