Michał Dudak

We're not adding any new features to this version of @mui/base. We moved the development of the library to the [new repo](https://github.com/mui/base-ui), and we're working on changing the components' API...

@TamirCode, please open a new issue and provide a reproduction.

Yes, this is being discussed in https://www.notion.so/mui-org/base-ui-Style-hooks-e943c3051ca74ce79f2e5af98a0f43eb

It's an expected behavior. When you use a keyboard to select multiple items, you don't want to be taken back to the beginning after selecting the first one and have...

OK, so it's inconsistent based on limiting the number of displayed options, I see. I'd say that the behavior with `limit` is better (as you can continue selecting more options...

@1CUNHA1, if the fix is contained only within Material UI (so the `useAutocomplete` hook) is not modified, then we'll likely be able to merge and release it. However, things may...

So, as I mentioned, we'll have to wait with the fix until we get to implement the Autocomplete in the Base UI repo.

This is so good! Thanks for working on it! I wonder if we still need the collapse/expand button. Or perhaps it can simply adjust the max height of the code...

Isn't it just a Core repo problem? If other repos use built packages from npm, we can still rely on pnpm. Or is there something more in the other repos...

> This requires an update on mui-base, but it's only a test file, so I figure it's no problem, right? No problem at all! I'll port this update to the...