\n \u003C/template>\n\n \u003Ctemplate #item=\"{ item }\">\n \u003Cspan v-text=\"item.label\" />\n \u003C/template>\n\u003C/UDropdownMenu>\n```",[3153,3156],{"name":3154,"color":3155},"question","d876e3",{"name":3157,"color":3158},"v3","49DCB8",4636,"nuxt","ui","open","DropdownMenu keyboard interaction handling","2025-07-31T06:44:47Z","https://github.com/nuxt/ui/issues/4636",0.7139063,{"description":3168,"labels":3169,"number":3177,"owner":3160,"repository":3161,"state":3162,"title":3178,"updated_at":3179,"url":3180,"score":3181},"### Description\n\nIs it possible for defineShortcuts to extend usingInput to allow function types to be passed in for dynamic focus condition management? For example, in the implementation of imperative shortcuts, defineShortcuts are defined centrally, handler dynamically executes different commands according to the global state, but usingInput currently only allows passing in Boolean and String values, and lacks the ability to change dynamically. It may be more flexible for usingInput to have dynamics than only supporting static capabilities in actual business.\n\n### Additional context\n\n_No response_",[3170,3173,3174],{"name":3171,"color":3172},"enhancement","a2eeef",{"name":3157,"color":3158},{"name":3175,"color":3176},"triage","ffffff",4356,"defineShortcuts usingInput extension function type","2025-06-16T12:21:26Z","https://github.com/nuxt/ui/issues/4356",0.73259073,{"description":3183,"labels":3184,"number":3187,"owner":3160,"repository":3161,"state":3162,"title":3188,"updated_at":3189,"url":3190,"score":3191},"### Description\n\nDear Contributors,\n\nNuxtUI has been a great help in my app development. Thank you very much.\n\nI would like to request the addition of a new feature. I would appreciate your consideration.\n\n\nCommon search engines provide a search bar with a suggestion feature.\nSelecting a keyword from the provided suggestions is optional; if a user does not select a suggestion, the content they have entered takes precedence.\n\nHowever, the current InputMenu specifications automatically select the first item on the list if the user doesn't make a selection, overwriting the user's input with that value.\nIt would be useful if there were a feature that limited the overwriting of user input to only cases where the user explicitly selects an item from the list.\n\nThank you.\n\n### Additional context\n\n_No response_",[3185,3186],{"name":3171,"color":3172},{"name":3175,"color":3176},4717,"InputMenu want to selection to optional","2025-08-12T05:38:55Z","https://github.com/nuxt/ui/issues/4717",0.7619396,{"description":3193,"labels":3194,"number":3200,"owner":3160,"repository":3161,"state":3162,"title":3201,"updated_at":3202,"url":3203,"score":3204},"### Environment\n\n```\n- Node Version: v20.12.0\n- Nuxt Version: 3.17.3\n- Runtime Modules: @nuxt/ui@3.3.3\n- Browser: Chromium 136 (windows)\n```\n\n#### Version\n\nv3.3.3\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/mutable-frog-xc2v8p\n\n### Description\n\nHello Nuxt Ui team!\n\nI noticed two issues with `USelect` & `USelectMenu`:\n\n1. **Input autofocus issue:** \n When typing in the input, opening the select causes the input to lose focus. Setting `:autofocus=\"false\"` has no effect, the select is still focused when opened.\n\n2. **Body lock issue:** \n Setting `:content=\"{ bodyLock: false }\"` does not prevent the body from being locked. The CSS property `pointer-events: default;` is still applied on the body.\n\nIn the case of an autocomplete, this prevents continuing to type in the input while still displaying suggested results.\n\nThanks for your help!\n",[3195,3198,3199],{"name":3196,"color":3197},"bug","d73a4a",{"name":3157,"color":3158},{"name":3175,"color":3176},4956,"`USelect` & `USelectMenu` setting :autofocus to false or :content `bodyLock` to false have no effect","2025-09-12T12:07:19Z","https://github.com/nuxt/ui/issues/4956",0.7621307,{"description":3206,"labels":3207,"number":3211,"owner":3160,"repository":3161,"state":3162,"title":3212,"updated_at":3213,"url":3214,"score":3215},"### Description\n\nhi,\n\ntest the use case here https://ui.nuxt.com/components/command-palette#with-custom-fuse-search\n\ntype any thing to search , move mouse up down , the options gets scroll , every thing is fine, \nthe use case is if user want to modify the input box query string, then user need to press arrow keys to go back to beginning of the input string , pressing Home does not work, i think pressing Home should take the cursor back to beginning of the input box!\n \n\n### Additional context\n\n_No response_",[3208,3209,3210],{"name":3171,"color":3172},{"name":3157,"color":3158},{"name":3175,"color":3176},4145,"[CommandPalette] move cursor to starting position in input box on pressing home","2025-05-13T18:38:18Z","https://github.com/nuxt/ui/issues/4145",0.77723914,{"description":3217,"labels":3218,"number":3222,"owner":3160,"repository":3223,"state":3162,"title":3224,"updated_at":3225,"url":3226,"score":3227},"### Environment\n\nThis is one of the environments i came across the problem:\r\n[11:15:23 AM] Working directory: /Users/lorenzorottigni/Documents/gitlab_private/portfolio.rottigni.tech\r\n[11:15:23 AM] Nuxt project info: (copied to clipboard)\r\n\r\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v18.13.0\r\n- Nuxt Version: 3.9.3\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: yarn@1.22.21\r\n- Builder: vite\r\n- User Config: ssr, debug, srcDir, serverDir, test, app, modules, css, postcss, unocss, tailwindcss, googleFonts, i18n, nitro, pwa, image, delayHydration, extensions, typescript, builder, vite, vue, runtimeConfig, devServer, sourcemap, experimental\r\n- Runtime Modules: @vueuse/nuxt@10.7.2, @nuxtjs/tailwindcss@6.10.4, @pinia/nuxt@0.5.1, @unocss/nuxt@0.58.3, @nuxtjs/i18n@8.0.0, @nuxt/image@1.3.0, nuxt-jsonld@2.0.8, @kevinmarrec/nuxt-pwa@0.17.0, @nuxtjs/google-fonts@3.1.3, nuxt-calendly@0.1.18, nuxt-delay-hydration@1.3.3, @nuxt/test-utils/module@3.10.0\r\n- Build Modules: -\r\n------------------------------\r\n\r\n[11:15:23 AM] 👉 Report an issue: https://github.com/nuxt/nuxt/issues/new\r\n\r\n👉 Suggest an improvement: https://github.com/nuxt/nuxt/discussions/new\r\n\r\n👉 Read documentation: https://nuxt.com\n\n### Reproduction\n\nThe crucial file is MyComponent.spec.ts:\r\nhttps://stackblitz.com/~/github.com/LorenzoRottigni/nuxt-test-utils-vitest-spy\n\n### Describe the bug\n\nI'm currently facing challenges in testing a component method within a Nuxt environment. Specifically, I'm attempting to spy on a component method to test its interactions within template events. Despite researching similar cases online, I've yet to find a clear solution to this issue.\r\n\r\nOne suggestion I encountered was to define the spy before the component mounts. However, I'm unable to access `wrapper.vm` before mount time, complicating this approach. Additionally, I experimented with spying on the global injected `$fetch` method from the 'ofetch' library. Unfortunately, this led to another error regarding the inability to redefine the variable `$fetch` when attempting variations like:\r\n\r\n```javascript\r\nimport OFetch from 'ofetch'\r\nconst spy = vi.spyOn(OFetch, '$fetch')\r\n// or\r\nconst spy = vi.spyOn(global, '$fetch')\r\n// or\r\nconst spy = vi.spyOn({ $fetch }, '$fetch')\r\n```\r\n\r\nIt appears that this issue may not be directly tied to the nuxt-test-utils package. Nevertheless, I wanted to bring it to your attention in the hopes that someone might offer guidance or assistance. I'm eager to find a resolution and would appreciate any insights or suggestions you might have.\r\n\r\nI'm also considering reporting a similar issue to the vue-test-utils package, as I suspect that this problem might be reproducible outside of the Nuxt environment.\r\n\r\nThank you for your time and assistance.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3219],{"name":3220,"color":3221},"pending triage","5D08F5",763,"test-utils","Unable to use vitest spy within nuxt 3 component methods.","2024-05-28T15:28:23Z","https://github.com/nuxt/test-utils/issues/763",0.77788454,{"description":3229,"labels":3230,"number":3233,"owner":3160,"repository":3161,"state":3234,"title":3235,"updated_at":3236,"url":3237,"score":3238},"### Environment\n\n------------------------------\n- Operating System: Windows_NT\n- Node Version: v20.15.0\n- Nuxt Version: 3.13.2\n- CLI Version: 3.14.0\n- Nitro Version: 2.9.7\n- Package Manager: pnpm@9.10.0\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Version\n\nv3.0.0-alpha.5\n\n### Reproduction\n\n No need. It'd be great if we had a stackblitz or codepen etc. playground example repo for v3 so that everyone can get a repo up quickly. It'd increase feedback.\n\n### Description\n\nWith v2 button text was automatically centered but now it is not? Is this expected because of radix-ui transition?\n\n```\n \u003CUButton type=\"submit\" block size=\"xl\">\n {{ $t(\"auth.login.action\") }}\n \u003C/UButton>\n```\n\n\n\n```\n \u003CUButton\n :label=\"$t('auth.login.actionKinder')\"\n type=\"submit\"\n block\n class=\"text-center\"\n size=\"xl\"\n />\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3231,3232],{"name":3154,"color":3155},{"name":3157,"color":3158},2317,"closed","Button 'block' attribute doesn't center it's content","2024-10-07T13:08:58Z","https://github.com/nuxt/ui/issues/2317",0.7408033,{"description":3240,"labels":3241,"number":3245,"owner":3160,"repository":3161,"state":3234,"title":3246,"updated_at":3247,"url":3248,"score":3249},"### Description\n\nAdd option to require a specific element to be hovered to trigger a shortcut.\n\n### Additional context\n\nIn my experience I often found it useful to limit the scope of a shortcut to specific element so that the user has to hover over the element and press so key/combination of keys.\n\nA good example could be a list of items that each has its own shortcut that will open it's detail drawer, modal... but only if the mouse is hovering the item in the list.\n\nI would like to implement this feature if it sounds interesting.",[3242,3243,3244],{"name":3171,"color":3172},{"name":3157,"color":3158},{"name":3175,"color":3176},4165,"`defineShortcuts` limit shortcut to a specific element","2025-06-11T15:47:21Z","https://github.com/nuxt/ui/issues/4165",0.7534903,{"description":3251,"labels":3252,"number":3262,"owner":3160,"repository":3161,"state":3234,"title":3263,"updated_at":3264,"url":3265,"score":3266},"### Description\n\nCurrently, I want to use the InputMenu for URL suggestions. The user can choose whether they want to select one of the suggestions or enter their own URL. There are several InputMenus, which means that the user usually wants to jump to the next field using the tab key. \n\nHowever, this is not so easy with the InputMenu. With `create-items`, the field expects a click or enter to be entered. There is no autocreate. \n\nI have also tried using `update:search-terms`, which worked well as long as the user treated it as a pure input field. However, in this case, no suggestions appear. And if the user selects a suggestion, the VModel is also empty – more precisely, it gets a value and is deleted shortly afterwards.\n\nTherefore, it would be desirable if create-items could be set to transfer the input to the V-Model immediately, or if there was a general mode in which the input field treats the suggestions as optional.\n\n\n\n### Additional context\n\n_No response_",[3253,3254,3257,3258,3259],{"name":3171,"color":3172},{"name":3255,"color":3256},"needs reproduction","CB47CF",{"name":3157,"color":3158},{"name":3175,"color":3176},{"name":3260,"color":3261},"closed-by-bot","ededed",4106,"InputMenu with Autocreate","2025-05-18T02:13:24Z","https://github.com/nuxt/ui/issues/4106",0.7537417,{"description":3268,"labels":3269,"number":3272,"owner":3160,"repository":3273,"state":3234,"title":3274,"updated_at":3275,"url":3276,"score":3277},"In my project, `google` is not recognised as a font provider even when the font exists on [google font](https://fonts.google.com/specimen/Archivo). Here is the configuration and the output:\n\n```ts\nexport default defineNuxtConfig({\n fonts: {\n families: [\n { name: 'Archivo', provider: 'google' },\n { name: 'My Font', provider: 'local' }\n ]\n },\n})\n```\n\n\n\nAdditionally, the code example playground [here](https://stackblitz.com/github/nuxt/fonts/tree/main/playground?file=package.json) from the docs has a different but potentially similar issue where the font providers aren't being initialised. \n\n\n\n",[3270],{"name":3255,"color":3271},"C94E53",438,"fonts","`google` is not recognised as a font provider","2024-12-27T15:26:16Z","https://github.com/nuxt/fonts/issues/438",0.7572414,["Reactive",3279],{},["Set"],["ShallowReactive",3282],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fI4vCWNwDqNZisNwT_5sJsrIZZ-uBvKaVxDaJ_d2DPfM":-1},"/nuxt/ui/4450"]