There are a couple of issues with the existing colors used in Button.kt which warrants a bit of an investigation. - [OutlinedButton](https://searchfox.org/firefox-main/rev/5ccf4a7d77a329f237d3a41e400049f9c47dc71f/mobile/android/android-components/components/compose/base/src/main/java/mozilla/components/compose/base/button/Button.kt#127-128) is currently relying on the button defaults, which differs from the [Figma](https://www.figma.com/design/MjufE1X5fvkxZ0YneX4kRd/Android-Library--2025-?node-id=53923-27460&m=dev). In the designs, OutlinedButton is using "Primary" text color vs "OnSurfaceVariant" from the defaults. We should check with UX whether or not the designs are out of date or whether we should continue to align with Figma designs as an intentional deviation from the defaults. - The current [DestructiveButton](https://searchfox.org/firefox-main/rev/5ccf4a7d77a329f237d3a41e400049f9c47dc71f/mobile/android/android-components/components/compose/base/src/main/java/mozilla/components/compose/base/button/Button.kt#165-166) implementation is using the colors of the [hovered state](https://www.figma.com/design/MjufE1X5fvkxZ0YneX4kRd/Android-Library--2025-?node-id=64529-34810&m=dev) from the Figma. We want to remove the background color so that it actually resembles the Enabled State https://www.figma.com/design/MjufE1X5fvkxZ0YneX4kRd/Android-Library--2025-?node-id=64529-34813&m=dev.
Bug 2003421 Comment 0 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
There are a couple of issues with the existing colors used in [Button.kt](https://searchfox.org/firefox-main/source/mobile/android/android-components/components/compose/base/src/main/java/mozilla/components/compose/base/button/Button.kt) which warrants a bit of an investigation. - [OutlinedButton](https://searchfox.org/firefox-main/rev/5ccf4a7d77a329f237d3a41e400049f9c47dc71f/mobile/android/android-components/components/compose/base/src/main/java/mozilla/components/compose/base/button/Button.kt#127-128) is currently relying on the button defaults, which differs from the [Figma](https://www.figma.com/design/MjufE1X5fvkxZ0YneX4kRd/Android-Library--2025-?node-id=53923-27460&m=dev). In the designs, OutlinedButton is using "Primary" text color vs "OnSurfaceVariant" from the defaults. We should check with UX whether or not the designs are out of date or whether we should continue to align with Figma designs as an intentional deviation from the defaults. - The current [DestructiveButton](https://searchfox.org/firefox-main/rev/5ccf4a7d77a329f237d3a41e400049f9c47dc71f/mobile/android/android-components/components/compose/base/src/main/java/mozilla/components/compose/base/button/Button.kt#165-166) implementation is using the colors of the [hovered state](https://www.figma.com/design/MjufE1X5fvkxZ0YneX4kRd/Android-Library--2025-?node-id=64529-34810&m=dev) from the Figma. We want to remove the background color so that it actually resembles the Enabled State https://www.figma.com/design/MjufE1X5fvkxZ0YneX4kRd/Android-Library--2025-?node-id=64529-34813&m=dev.