[Bug Report][3.11.1] VListItem :disabled doesn't allow VList vmodel:selected to update

[Estheisia]

Environment

Vuetify Version: 3.11.1, 3.10 also
Vue Version: 3.5.25
OS: Ubuntu undefined (current)

Steps to reproduce

1. Click on the button to toggle the boolean to able the VListItem
2. Click on some VListItem in order to select them
3. It fails to update the vmodel (maybe it doesn't update some internal states ?)

Expected Behavior

The VListItem should, upon clicking, update the vmodel of the VList after being abled

Actual Behavior

The event, upon clicking, fires but doesn't update the vmodel after being abled

Reproduction Link

https://play.vuetifyjs.com/#...

Images

[KaelWD]

#20962

[Estheisia]

Also, if in a VList you put a VListItem with a :disabled then you can, through tab/arrow navigation, select it and press enter to navigate with its to="/url" prop despite being unclickable.

You'll be able to tab to reach the 1st VListItem, then with arrow on 2nd (disabled or not) and 3rd, if you tab again instead of going to the next element after the VList, you go on the next disabled VListItem :

Simplified version :

<v-navigation-drawer>
  <v-list>
    <v-list-item>Prop and All 1</v-list-item>
    <v-list-item :disabled="someBoolean">Prop and All 2</v-list-item>
    <v-list-item>Prop and All 3</v-list-item>
  </v-list>
</v-navigation-drawer>

Real VListItem exemple :

<v-navigation-drawer>
  <v-list>
      <v-list-item
          v-if="canSeeDocuments"
          key="nav_document"
          to="/documents"
          prepend-icon="mdi-file-document-outline"
          :title="$t('app.label.documents')"
          v-tooltip:right="$t('app.label.documents')"
      />
    <v-list-item
          v-if="canSeeSuggestions"
          key="nav_suggestions"
          :disabled="!canSuggestions"
          to="/suggestions"
          prepend-icon="mdi-lightbulb-on-outline"
          :title="$t('app.label.suggestions')"
          v-tooltip:right="$t('app.label.suggestions')"
      />
  </v-list>
</v-navigation-drawer>

I don't know if it is the same bug, seemed related