angular
bug(MatButton): FAB with disabled state using alpha on background collisions
Is this a regression?
- [ ] Yes, this behavior used to work in the previous version
The previous version in which this bug was not present was
No response
Description
Because the disabled state background color is defined with alpha, FAB collide with page contents when disabled. There's no guideline anywhere stating that FAB should never get disabled, and a disabled FAB is even part of the documentation.
FAB stands for Floating Action Button according to https://m3.material.io/components/floating-action-button/overview so it should be assumed most uses will be with absolute or fixed positioning.
Reproduction
StackBlitz link: https://stackblitz.com/edit/4rnhsm?file=src%2Findex.html,src%2Fexample%2Fbutton-overview-example.html,src%2Fexample%2Fbutton-overview-example.css Steps to reproduce:
- Have a FAB button
- Make it disabled
Expected Behavior
The button doesn't get visually mixed with the page contents. One potential solution would be to make the disabled state not use alpha.
Actual Behavior
Page contents as partially visible background on the button decrease its readability.
Environment
- Angular: 17.0
- CDK/Material: 17.0
- Browser(s): any
- Operating System (e.g. Windows, macOS, Ubuntu): any
To work around this problem in the meantime, you can place the fab in a container with a white background color https://stackblitz.com/edit/4rnhsm-fbbxhq
Alternative workaround (which we used) is --mdc-filled-button-disabled-container-color: some-solid-color