[ToggleButton] Provide unstyled/headless API for heavy customization

I’d like to style a <ToggleButton> to look and behave exactly like a <Button> without explicitly overriding all of the ToggleButton’s class styles.

I’ve learned that I can inject Button styles this way:

<ToggleButton
  classes={{
    root: 'MuiButtonBase-root MuiButton-root MuiButton-contained MuiButton-containedSecondary MuiButton-disableElevation',
    selected: 'MuiButton-root:hover MuiButton-containedSecondary:hover MuiButton-disableElevation:active MuiButton-disableElevation:hover MuiButton-contained:active MuiButton-contained:hover',
  }}
>

This halfway solves my problem. However, I’d like to avoid injecting the classes MuiToggleButton-root MuiToggleButtonGroup-grouped MuiToggleButtonGroup-groupedHorizontal because they’re overriding the ones I’ve added above.

Is this sort of thing possible? The reason I’m trying this is because I can’t put a <Button> inside of a <ToggleButton> without getting an error, so I figured I’d try to make it look and behave like a <Button>.

Thanks

[oliviertassinari]

This makes me think about:

1. ButtonGroup and ToggleButton are very close in UI. We could have almost built ToggleButton on top of ButtonGroup.
2. ToggleButton adds functionality over ButtonGroup. In #17203 we explore how to improve the a11y.
3. Maybe we could extract the ToggleButton behavior into a headless hook, and expose it, which would allow @dungle-scrubs to implement the same behavior with a Button. I doubt that an unstyled component API would work for this use case.
4. Reading https://www.w3.org/TR/wai-aria-practices/examples/toolbar/toolbar.html, the hook we need might even be at the radio level, not sure.

[mnajdova]

Got it yes, sounds like something that will be possible with the unstyled components. Until then, we don’t have option to reset styles.