Skip to content
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

Buttons have incorrect styles in 7.1.0 #1874

Closed
edenman opened this issue Nov 23, 2020 · 4 comments
Closed

Buttons have incorrect styles in 7.1.0 #1874

edenman opened this issue Nov 23, 2020 · 4 comments

Comments

@edenman
Copy link
Contributor

edenman commented Nov 23, 2020

Step 2: Describe your environment

  • FirebaseUI version: 7.1.0

Step 3: Describe the problem:

Steps to reproduce:

  1. Customize button appearance by overriding styles
  2. Update from 6.2 to 7.1
  3. Buttons are no longer styled appropriately

Here's how I'm doing the customization:

<style name="FirebaseUI.Button.AccountChooser.GoogleButton">
  <item name="drawableStartCompat">@drawable/ic_sign_in_google</item>
  <item name="android:background">@color/auth_button_bg_google</item>
  <item name="android:textColor">@color/actually_white</item>
</style>

I checked and the style hasn't changed names or anything:

<style name="FirebaseUI.Button.AccountChooser.EmailButton">

Looks like this is happening because of a switch from com.firebase.ui.auth.util.ui.SupportVectorDrawablesButton to Button in 5342e3d . I can get it working again if I use drawableLeft but obviously that's not ideal for RTL users. What was the motivation for that change? It seems to have even broken the default UI. If I remove all my style customizations, here's what the screen looks like:
Screenshot_1606165952

@edenman edenman changed the title Customization of buttons via styles.xml doesn't work in 7.1.0 Buttons have incorrect styles in 7.1.0 Nov 23, 2020
@DeweyReed
Copy link

Same here. It seems MDC changes <Button> to MaterialButton, and then styles are lost.

@samtstern samtstern added this to the 7.1.1 milestone Nov 24, 2020
@samtstern
Copy link
Contributor

@edenman @DeweyReed thanks for reporting this. That change was just a cleanup, if it's breaking we can revert it for version 7.1.1.

@samtstern
Copy link
Contributor

This has been fixed and released in version 7.1.1

@edenman
Copy link
Contributor Author

edenman commented Dec 6, 2020

Confirmed: fixed in 7.1.1

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants