Package

v3.18

Description

Hello,
I've been using Nuxt UI for many months and I really love it!

However, I've often run into limitations with the InputMenu component, because its behavior feels too close to the SelectMenu.

The main difference (at least for me) is that since it's an input, the priority should be the input value itself. But currently, it behaves more like the SelectMenu, where the value must exist in the provided :items in order to be set. The text entered in the field is only treated as a search term, and it is not updated in the bound ref — while it should be, since this is supposed to be an input.

I think the InputMenu should allow any value typed by the user to be stored and displayed, even if it’s not present in the :items list. This would make it much more flexible and closer to the expected behavior of an input field.

For example, in this InputMenu example, if i start to type 'Hello', the ref value still remains 'Backlog'...
This is the excepted behaviour for a SelectMenu, but for a InputMenu, the ref value should become 'Hello':

And for me the :create-item option doesn’t solve this case, because from a UX perspective it doesn’t behave like a true input. The input value shouldn’t require extra steps to be reflected in the bound ref.

I'm curious about your point of view, and if you agree with me,
would it be possible to adjust this behavior, or at least provide an option to allow free input values?

Thanks a lot for your work!