Skip to content

Conversation

@manabu-nakamura
Copy link
Contributor

<com.google.android.material.button.MaterialButtonToggleGroup
    app:selectionRequired="true"
    app:singleSelection="true"/>


⬇️

<com.google.android.material.button.MaterialButtonGroup
    style="@style/Widget.Material3Expressive.MaterialButtonGroup.Connected"
    app:overflowMode="menu"/>

@dsn5ft
Copy link
Contributor

dsn5ft commented Jul 31, 2025

Hi! According to our designers / spec, when using toggle buttons it's best to wrap them to the next line as opposed to putting toggle buttons into an overflow. This is because toggle buttons in a group are all very related to each other, and it's important to show them all together on screen.

We're currently considering providing a wrap option for the button group component, and we'll update the catalog to use that if it works out.

@dsn5ft dsn5ft closed this Jul 31, 2025
@manabu-nakamura manabu-nakamura deleted the buttongroup branch July 31, 2025 22:41
@manabu-nakamura
Copy link
Contributor Author

https://github.com/material-components/material-components-android/blob/master/docs/components/ToggleButtonGroup.md:

Toggle button group (Segmented buttons) ...

https://m3.material.io/components/segmented-buttons/overview:

Segmented buttons are being deprecated in the Material 3 expressive update.

MaterialButtonToggleGroup isn't deprecated, right?

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants