[Bug Report][3.8.5] VAutocomplete with hide-details="auto" does not update menu position when validation error state changes

[wumingqin]

Environment

Vuetify Version: 3.8.5
Vue Version: 3.5.14
OS: Windows 10 (current)

Steps to reproduce

1. Place a VAutocomplete component with the mentioned props inside a VDialog.
2. Trigger validation error
3. Open the autocomplete dropdown. The menu position accounts for the visible error message.
4. Select a valid item(s), causing the validation error to clear and the error message to hide.
5. The menu position does not adjust upward and remains offset downward.

Expected Behavior

The dropdown menu (VMenu) of the VAutocomplete component should automatically update its position whenever the visibility of the hide-details area (error or hint messages) changes, ensuring it remains correctly aligned with the bottom of the input field.

Actual Behavior

When a VAutocomplete component (with chips, multiple, hide-details="auto" and validation rules) is placed inside a VDialog component, its dropdown menu (VMenu) does not update its position when the validation error message disappears after a valid selection is made. The menu appears to be "stuck" at the position it would have been if the error message was still visible, causing a visual misalignment

Reproduction Link

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

Images

[jcjp]

I tried your reproduction and followed your instruction and it seems that after the error is shown and then select an item, it does go back to the original position without any errors could you provide a recording of the issue that you are describing thanks!

[J-Sek]

chips do not matter. VMenu uses location-strategy "connected" that is reacting to a limited number of variables and won't make the dropdown follow the field in situations like this.

• workaround 1 - toggle offset between 0 and 0.1 to force updateLocation
• workaround 2 - offset hack tied to the error state, suitable for a reusable wrapper around any field with a dropdown

Not sure if Vuetify should have this level of coupling though... Theoretically, we could introduce a new location-strategy="follow" and apply MutationObserver or simply call getBoundingClientRect for the menu target with some interval. It would introduce overhead and won't be a default.