\n \u003C/template>\n\n \u003Ctemplate #item=\"{ item }\">\n \u003Cspan v-text=\"item.label\" />\n \u003C/template>\n\u003C/UDropdownMenu>\n```",[3191,3194],{"name":3192,"color":3193},"question","d876e3",{"name":3162,"color":3163},4636,"DropdownMenu keyboard interaction handling","2025-07-31T06:44:47Z","https://github.com/nuxt/ui/issues/4636",0.75310147,{"description":3201,"labels":3202,"number":3208,"owner":3168,"repository":3169,"state":3170,"title":3209,"updated_at":3210,"url":3211,"score":3212},"",[3203,3204,3205],{"name":3159,"color":3160},{"name":3162,"color":3163},{"name":3206,"color":3207},"reka-ui","56d799",2337,"[DropdownMenu/Popover/Tooltip] Improve arrow styling like `NavigationMenu` ","2024-10-08T10:12:48Z","https://github.com/nuxt/ui/issues/2337",0.76553226,{"description":3214,"labels":3215,"number":3218,"owner":3168,"repository":3169,"state":3170,"title":3219,"updated_at":3220,"url":3221,"score":3222},"### Package\n\nv3.18\n\n### Description\n\nHello,\nI've been using Nuxt UI for many months and I really love it!\n\nHowever, I've often run into limitations with the `InputMenu` component, because its behavior feels too close to the `SelectMenu`.\n\nThe 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**.\n\nI 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.\n\nFor example, in this `InputMenu` example, if i start to type 'Hello', the **ref** value still remains 'Backlog'... \nThis is the excepted behaviour for a `SelectMenu`, but for a `InputMenu`, the **ref** value should become 'Hello':\n\n\n\nAnd 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**.\n\nI'm curious about your point of view, and if you agree with me, \nwould it be possible to adjust this behavior, or at least provide an option to allow free input values?\n\nThanks a lot for your work!",[3216,3217],{"name":3192,"color":3193},{"name":3162,"color":3163},4859,"InputMenu behaves like a SelectMenu instead of a true input – needs proper input behavior","2025-09-13T11:12:57Z","https://github.com/nuxt/ui/issues/4859",0.76692,{"description":3224,"labels":3225,"number":3236,"owner":3168,"repository":3168,"state":3170,"title":3237,"updated_at":3238,"url":3239,"score":3240},"### Describe the feature\r\n\r\nThe current behavior of `default` is inconsistent with other composables such as `useFetch`, `useAsyncData` and `useState`:\r\n1. `default` value is used only on init.\r\n2. `default` value is set to cookies in SSR, but not in CSR (https://github.com/nuxt/nuxt/issues/26701).\r\n\r\nProposals (breaking):\r\n1. The default value must be used even if the value is later set to `null` or `undefined`:\r\n```ts\r\nconst foo = useCookie('foo', { default: () => 'Stark' })\r\nfoo.value // -> 'Stark'\r\nfoo.value = 'Hulk'\r\nfoo.value // -> 'Hulk'\r\nfoo.value = undefined\r\nfoo.value // -> 'Stark' because it is default\r\n```\r\nJust as it is done for `useFetch` - if the `data` is undefined or it is an error, default value is used.\r\nAlso, good examples are [Vue prop default value](https://vuejs.org/guide/components/props.html#prop-validation) and https://vueuse.org/shared/refDefault.\r\n\r\n2. or rename `default` to `init` to match `useState` where default data is only used once during initialization.\r\n\r\nIn all cases default value should not be set to cookies on init.\r\n\r\n### Additional information\r\n\r\n- [X] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3226,3229,3230,3233],{"name":3227,"color":3228},"discussion","538de2",{"name":3179,"color":3180},{"name":3231,"color":3232},"🔨 p3-minor","FBCA04",{"name":3234,"color":3235},"4.x","3B01A5",26760,"Change behavior of `default` in `useCookie` to be consistent with other composables","2024-04-23T11:33:41Z","https://github.com/nuxt/nuxt/issues/26760",0.7716099,{"description":3242,"labels":3243,"number":3247,"owner":3168,"repository":3169,"state":3248,"title":3249,"updated_at":3250,"url":3251,"score":3252},"### Environment\n\nNuxt UI pro v 3.1.0\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.0\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/input-menu#control-search-term\n\n### Description\n\nHello, \n\nI am reopening an issue based on https://github.com/nuxt/ui/issues/3782\n\nI still have an issue on the InputMenu that filters with the default value.\n\nAs a reproduction : we can see the same behavior I am facing in the documentation : https://ui.nuxt.com/components/input-menu#control-search-term . \n\n1) => The first click on InputMenu shows only the seacherd term (here Backlog)\n2) => If I close the popover and reopen it a second time, it shows the entire list.\n\nI tried the :reset-search-term-on-select=\"false\" , it allows to display the entire list at 1st click but it leads to not showing the default selected value (the placeholder is displayed).\n\nActually, I am looking to display the entire list at first click, even if a value is already selected.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3244,3245,3246],{"name":3179,"color":3180},{"name":3162,"color":3163},{"name":3206,"color":3207},3993,"closed","InputMenu Clear Search on Select at first click","2025-07-16T10:57:06Z","https://github.com/nuxt/ui/issues/3993",0.7246176,{"description":3254,"labels":3255,"number":3259,"owner":3168,"repository":3169,"state":3248,"title":3260,"updated_at":3261,"url":3262,"score":3263},"### Version\n\nLatest commit https://pkg.pr.new/@nuxt/ui@62ab016\n\n### Description\n\nWhen fetching items using [ignore-filter prop ](https://ui.nuxt.com/components/select-menu#with-ignore-filter) `\u003CUSelectMenu>` does not remember the current selection.\n\nCurrently it works only if the selected item stays in the items array which is barely the case if dealing with more than 10 items:\n\nhttps://github.com/user-attachments/assets/f5c6b264-52a5-4d8b-b015-242e36d91fdb\n\nThis happens in two cases:\n\n1. When selecting an item the searchTerm gets resetted, the items-array changes and the selected item is no more in it -> Select menu label becomes empty\n2. When an item is selected, but searching for other items that dont include seleced item -> Select menu label becomes empty\n\n### Reproduction\n\nAlso reproducable in the docs:\nhttps://ui.nuxt.com/components/select-menu#with-ignore-filter\n\nhttps://github.com/user-attachments/assets/ec3065bb-7cc2-4976-9dde-da99dd2311b6\n\nHere case 1 never happens because the jsonplaceholder-api only has just 5 user-items so the selected user is always in the default empty search result. BUT case 2 happens: Select a user, open select again, type in any other name that doesnt include first user -> Select menu label becomes empty (weirdly tho, the avatar stays)",[3256,3257,3258],{"name":3179,"color":3180},{"name":3162,"color":3163},{"name":3165,"color":3166},4582,"SelectMenu with fetched items (ignore-filter) doesnt remember current selection","2025-08-14T09:04:53Z","https://github.com/nuxt/ui/issues/4582",0.7371208,{"description":3265,"labels":3266,"number":3269,"owner":3168,"repository":3169,"state":3248,"title":3270,"updated_at":3271,"url":3272,"score":3273},"### Description\n\nAfter updating to 3.1.0 \"TableColumn\" cant be imported from @nuxt/ui\nonly from @nuxt/ui/runtime/components/Table.vue.js\n\n",[3267,3268],{"name":3192,"color":3193},{"name":3162,"color":3163},3980,"Bug? TableColumn import type from @nuxt/ui not possible?","2025-04-25T09:44:12Z","https://github.com/nuxt/ui/issues/3980",0.73746544,{"description":3201,"labels":3275,"number":3278,"owner":3168,"repository":3279,"state":3248,"title":3280,"updated_at":3281,"url":3282,"score":3283},[3276],{"name":3179,"color":3277},"ff281a",164,"nuxt.com","`USelect` default value is not displayed after ssr load","2023-02-15T12:31:49Z","https://github.com/nuxt/nuxt.com/issues/164",0.7425416,["Reactive",3285],{},["Set"],["ShallowReactive",3288],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fHakP8-f-ZxXn1zjmlc8FTWP7cjyY7YrUv_nb4UDUpnw":-1},"/nuxt/ui/2257"]