Michał Dudak

Another idea - how about including the button in the Menu component itself (both Unstyled and Joy)? It would remove the confusion and make things simpler for users. For cases...

> Using button as a root slot would not work well Perhaps the root slot could be a Fragment by default. I've taken a look at what the other libraries...

As for Option 4 and your worry about a breaking change - MenuUnstyled has already departed from what was in Material UI. Its implementation was completely rewritten, so we have...

I believe this behavior is inherent to Firefox - whenever another element is focused, the selection is lost. This isn't specific to Material UI. Proof: https://jsbin.com/jovakuyimu/1/edit?html,js,output

We do support Firefox. As I stated above, this issue is not specific to Material UI. We can't control Firefox's internal behavior. I'm not aware of any workarounds for this.

@kaguya3222 Would applying `disableClearable` conditionally work for your case? For example `disableClearable={value !== null}`

@mui/core, @oliviertassinari, @mbrookes we haven't merged in these changes for a long while. There were a lot of conflicts in translated files with `master` which I resolved by accepting the...

When we have the MenuButton component, this logic will be built in. For now, we have to fall back to this fix.

@mnajdova is this good to be merged now?

> We could try to adopt the styles to some of the components that we have inside @mui/material-next - this is our experimental package that depends on @mui/base that we...