[Autocomplete] It triggers onChange when the input value is an empty string about material-ui HOT 3 OPEN

Autocomplete in non freeSolo mode should only provide valid options. The behavior is not to automatically select a value as the user types, but when the user confirms it via different interaction methods. This however is not true for the empty value "option". This is applied as value change instantly as the user types.

Example where it is a problem: you track the autocomplete value for changes, without controlling the value (update: its actually synced initially, but does not matter in the case, ignore). You want to execute a navigation when the user picks an item. However, now the user wants to clear the input and type something else, the navigation is executed with an empty value. The empty value is valid in the navigation, so I can't just filter it out, but its not intended to trigger when the user simply wants to search and remove the term he has in the autocomplete.

PS. I can start track to figure out how the clear happened, but my intuition tells me that its maybe not correct for it to behave differently in this case

from material-ui.

@akomm @danilo-leal @mj12albert @zannager where can i find the file where the issue is actually reported. can u please specify the file directory

from material-ui.

I don't understand the issue. The current behavior looks correct. It's not clear why it should behave differently. Why?

Is this about the trigger happening when the action happens and not on blur? I suspect we have other issues about this topic. It the same idea as to why use onClick and not onMouseDown: to be easier to cancel the action.

note: package scope removed, it's about the Autocomplete component itself, not Material UI styles

from material-ui.