deleted, closed

[giuliohome]

fixes: #20718

Description

As per my comment here, I have deleted the problematic if condition and I have also tested again the reproduction (non regression) of #19929 in the playground reported below

Markup:

<template>
  <v-app>
    <v-container>
      <v-autocomplete
        v-model="selection"
        :items="items"
        clearable
        placeholder="select a item"
      ></v-autocomplete>
      <v-btn @click="myResetAction">reset</v-btn>
      <v-autocomplete
        v-model="selected"
        :items="items2"
        auto-select-first
        clearable
      ></v-autocomplete>
      <span>Selected: {{ selected }}</span>
    </v-container>    
  </v-app>
</template>

<script setup>
  import { ref } from 'vue'

  const selection = ref()
  const items = ref(['itemA', 'itemB'])

  const items2 = ref(['Option 1', 'Option 2', 'Option 3'])

  const selected = ref(null)

  const myResetAction = () => {
    selection.value = undefined
  }
</script>

[J-Sek]

It will revert the fix for #19543 but I think it is fine. To suppress unnecessary server calls devs should keep track of the menu state with v-model:menu="isMenuOpen" and abort processing if menu is closed (it may need additional debounce, but I guess it would be there anyway).

This playground illustrates my point.

Previous implementation also was handling very narrow case. User can select "Item A", type additional letters and then blur. The resulting search is null and is set back to "Item A" on focus. For the fix to be consistent it would need to reset search to the model on blur... but then it is not a result of user typing and we are in the square one - trying to bend to invalid expectations.

I vote for this PR to be merged and additional example in the docs for "lazy" suggestions.