[Autocomplete] clearOnBlur is not working

[ghost]

• The issue is present in the latest release.
• I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯

On Autocomplete with multiple enabled, clearOnBlur doesn't work as the docs say it should: "Set to false if you want to help the user resume his search."

Expected Behavior 🤔

The Autocomplete's input field should not clear on blur or option select when clearOnBlur is set to false, even when the Autocomplete component has the multiple option enabled. If the docs say that it helps the user resume his/her search, the input should not be cleared on blur, no matter the type of Autocomplete.

Steps to Reproduce 🕹

Steps:

1. Check the demo forked from MUI 5.0 docs: https://codesandbox.io/s/tags-material-demo-forked-ccjcs
2. Enter an input and move away from the input (click outside of the input or select an item).
3. The input clears, even though clearOnBlur={false} is set on all three Autocompletes.

Context 🔦

I've been utilizing onInputChange, inputValue, and onChange to accomplish this behavior, but it's extremely laggy and slow because my dropdown has a lot of options. Reducing the number to only 100 using filterOptions hasn't done much to help, but the clearOnBlur would handle everything I'm manually handling in onInputChange and inputValue much more cleanly.

Your Environment 🌎

@emotion/react -- latest (11.4.1)
@emotion/styled -- latest (11.3.0)
@mui/material -- latest (5.0.2)
react -- latest (17.0.2)
react-dom -- latest (17.0.2)

Chrome 94.0.4606.61

[hbjORbj]

@wiznotwiz Thanks for the report. In fact, clearOnBlur is not working even if you are not enabling multiple prop. See https://codesandbox.io/s/migd6?file=/demo.js

The Autocomplete's input field should not clear on blur or option select when clearOnBlur is set to false

In fact, on option select, input field should not clear even if clearOnBlur is set to false.

Since it works well on v4: https://codesandbox.io/s/material-demo-forked-swu2z?file=/demo.js, this seems to be a v5 bug. I will look into it.