\n \u003C/template>\n\u003C/UModal>\n```\n\n\n### Description\n\nselect menu's search input always autofocus inside modal, even when the autofocus is set to false.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3168,3169,3170,3171,3174],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},{"name":3172,"color":3173},"closed-by-bot","ededed",{"name":3175,"color":3173},"stale",3933,"closed","SelectMenu's autofocus doesn't work inside Modal","2025-08-12T02:12:37Z","https://github.com/nuxt/ui/issues/3933",0.6673494,{"description":3183,"labels":3184,"number":3189,"owner":3147,"repository":3148,"state":3177,"title":3190,"updated_at":3191,"url":3192,"score":3193},"### Environment\n\nnuxt: 3.15.1\n\n### Version\n\nv2.20.0\n\n### Reproduction\n\n-\n\n### Description\n\n```\n\u003CUModal>\n \u003CUInput v-model=\"state.name\" placeholder=\"..\" />\n \u003CUInput v-model=\"state.name1\" placeholder=\"...\" />\n\u003C/UModal>\n```\n\nWhen a modal contains one or more input boxes, the first input box will always get focus automatically.\nIf I manually add a close button in the upper right corner, it will trigger a validation when I click it. This is not good. How can I avoid the input box getting focus when opening the modal?\n\n### Additional context\n\n\n\n\n### Logs\n\n```shell-script\n\n```",[3185,3186,3187,3188],{"name":3138,"color":3139},{"name":3144,"color":3145},{"name":3172,"color":3173},{"name":3175,"color":3173},3062,"The input box in the modal will automatically gain focus","2025-06-18T09:02:39Z","https://github.com/nuxt/ui/issues/3062",0.66855717,{"description":3195,"labels":3196,"number":3200,"owner":3147,"repository":3148,"state":3177,"title":3201,"updated_at":3202,"url":3203,"score":3204},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.20.3\r\n- Nuxt Version: 3.12.1\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.6\r\n- Package Manager: pnpm@8.15.6\r\n- Builder: -\r\n- User Config: modules\r\n- Runtime Modules: @nuxt/ui@2.17.0\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Version\r\n\r\nv2.17.0\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-ui-5movd8?file=app.vue\r\n(Test on mobile or open Devtools and toggle device mode.)\r\n\r\n### Description\r\n\r\nWhen two or more `UModal` are using `preventClose` prop doesn't allow to interact with the elements of the modal on top when in touch mode.\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3197,3198,3199],{"name":3138,"color":3139},{"name":3172,"color":3173},{"name":3175,"color":3173},1932,"`UModal` preventClose doesn't allow to interact with elements","2025-06-19T02:12:17Z","https://github.com/nuxt/ui/issues/1932",0.6939512,{"description":3206,"labels":3207,"number":3214,"owner":3147,"repository":3148,"state":3177,"title":3215,"updated_at":3216,"url":3217,"score":3218},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.8\n- Package Manager: pnpm@10.7.1\n- Builder: -\n- User Config: modules, plugins, devtools, css, runtimeConfig, compatibilityDate, eslint\n- Runtime Modules: @nuxt/ui@3.0.2, @nuxt/eslint@1.2.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nV3.0.2\n\n### Reproduction\n\nhttps://github.com/user-attachments/assets/96d306b8-967d-4d16-841d-bffe9d6b0fa0\n\n### Description\n\nSelect component no longer receives focus properly, which breaks keyboard navigation (e.g. using Tab or arrow keys to open and navigate the options). \n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3208,3209,3212,3213],{"name":3138,"color":3139},{"name":3210,"color":3211},"needs reproduction","CB47CF",{"name":3141,"color":3142},{"name":3144,"color":3145},3791,"Focus no longer works on Select component","2025-04-30T13:25:54Z","https://github.com/nuxt/ui/issues/3791",0.7041431,{"description":3220,"labels":3221,"number":3224,"owner":3147,"repository":3148,"state":3177,"title":3225,"updated_at":3226,"url":3227,"score":3228},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v23.11.0\n- Nuxt Version: -\n- CLI Version: 3.25.0\n- Nitro Version: -\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.2\n\n### Reproduction\n\nhttps://github.com/CorruptionTiger/app-1.git\n\n### Description\n\nThe button operation in the dropdown menu cannot make the page elements focus.\n\n### Additional context\n\nClick the button on the webpage. Ordinary buttons can correctly make the input focus, but buttons in the dropdown menu cannot make the input focus.\n\n### Logs\n\n```shell-script\nThe button operation in the dropdown menu cannot make the page elements focus.\n```",[3222,3223],{"name":3138,"color":3139},{"name":3141,"color":3142},3968,"Accessibility and focus.","2025-09-09T14:50:00Z","https://github.com/nuxt/ui/issues/3968",0.70780545,{"description":3230,"labels":3231,"number":3235,"owner":3147,"repository":3148,"state":3177,"title":3236,"updated_at":3237,"url":3238,"score":3239},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: ^3.17.5\n- CLI Version: 3.25.1\n- Nitro Version: -\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: devtools, modules, css, future, compatibilityDate, formkit\n- Runtime Modules: @nuxt/ui@^3.1.3, @nuxt/eslint@^1.4.1, @formkit/nuxt@^1.6.9\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.3\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/gallant-scooby-hcy72z\n\n### Description\n\nI am upgrading my app to use Nuxt UI v3 and am having issues with `UModal` and [FormKit](https://formkit.com/).\n\nI am unable to open a modal with a FormKit modal inside of it. I get the following error.\n\n\u003Cimg width=\"557\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/dc0baba8-ed91-4006-9164-5e9e1fa6c67a\" />\n\nI believe this is an issue with Nuxt UI and not FormKit because it used to work fine on the previous version.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nindex.vue:17 [Vue warn]: Unhandled error during execution of mounted hook \n at \u003CDialogTrigger key=0 as-child=\"\" class=\"\" > \n at \u003CDialogRoot modal=true open=true onAfter:leave=fn ... > \n at \u003CUModal close= {onClick: ƒ} title=\"This modal was opened programmatically 0 times\" open=true ... > \n at \u003CModalExample key= Symbol(useOverlay) ref_for=true count=0 ... > \n at \u003CUOverlayProvider > \n at \u003CTooltipProvider > \n at \u003CConfigProvider use-id=fn\u003Cuse-id> dir=undefined locale=undefined > \n at \u003CApp > \n at \u003CApp key=4 > \n at \u003CNuxtRoot>\nwarn$1 @ runtime-core.esm-bundler.js?v=fb91d406:50\nlogError @ runtime-core.esm-bundler.js?v=fb91d406:261\nhandleError @ runtime-core.esm-bundler.js?v=fb91d406:253\ncallWithErrorHandling @ runtime-core.esm-bundler.js?v=fb91d406:199\ncallWithAsyncErrorHandling @ runtime-core.esm-bundler.js?v=fb91d406:204\nhook.__weh.hook.__weh @ runtime-core.esm-bundler.js?v=fb91d406:2842\nflushPostFlushCbs @ runtime-core.esm-bundler.js?v=fb91d406:382\nflushJobs @ runtime-core.esm-bundler.js?v=fb91d406:424\nPromise.then\nqueueFlush @ runtime-core.esm-bundler.js?v=fb91d406:319\nqueueJob @ runtime-core.esm-bundler.js?v=fb91d406:314\neffect2.scheduler @ runtime-core.esm-bundler.js?v=fb91d406:5499\ntrigger @ reactivity.esm-bundler.js?v=fb91d406:235\nendBatch @ reactivity.esm-bundler.js?v=fb91d406:293\ntrigger @ reactivity.esm-bundler.js?v=fb91d406:693\nset @ reactivity.esm-bundler.js?v=fb91d406:974\nopen @ useOverlay.js?v=fb91d406:29\nopen @ useOverlay.js?v=fb91d406:18\nopen @ index.vue:17\n(anonymous) @ Button.vue:80\nonClickWrapper @ Button.vue:80\nonClickWrapper @ LinkBase.vue:30\ncallWithErrorHandling @ runtime-core.esm-bundler.js?v=fb91d406:197\ncallWithAsyncErrorHandling @ runtime-core.esm-bundler.js?v=fb91d406:204\ninvoker @ runtime-dom.esm-bundler.js?v=fb91d406:720\nuseForwardExpose.js?v=fb91d406:8 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'nodeName')\n at ComputedRefImpl.fn (useForwardExpose.js?v=fb91d406:8:64)\n at refreshComputed (reactivity.esm-bundler.js?v=fb91d406:361:29)\n at get value (reactivity.esm-bundler.js?v=fb91d406:1567:5)\n at DialogTrigger.js?v=fb91d406:19:57\n at runtime-core.esm-bundler.js?v=fb91d406:2862:40\n at callWithErrorHandling (runtime-core.esm-bundler.js?v=fb91d406:197:19)\n at callWithAsyncErrorHandling (runtime-core.esm-bundler.js?v=fb91d406:204:17)\n at hook.__weh.hook.__weh (runtime-core.esm-bundler.js?v=fb91d406:2842:19)\n at flushPostFlushCbs (runtime-core.esm-bundler.js?v=fb91d406:382:28)\n at flushJobs (runtime-core.esm-bundler.js?v=fb91d406:424:5)\n```",[3232,3233,3234],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},4309,"UModal does not work with FormKit","2025-06-07T23:36:34Z","https://github.com/nuxt/ui/issues/4309",0.711521,{"description":3241,"labels":3242,"number":3249,"owner":3147,"repository":3147,"state":3177,"title":3250,"updated_at":3251,"url":3252,"score":3253},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v18.18.2`\r\n- Nuxt Version: `3.6.1`\r\n- Nitro Version: `2.5.2`\r\n- Package Manager: `npm@9.8.1`\r\n- Builder: `vite`\r\n- User Config: `ssr`, `nitro`, `app`, `modules`, `security`, `vite`\r\n- Runtime Modules: `nuxt-security@1.0.0-rc.2`, `nuxt-vitest@0.10.2`\r\n- Build Modules: `-`\r\n\r\n\r\nAlthough we are pinned at Nuxt v3.6.1 'for reasons' the bug can be observed in StackBlitz repro on Nuxt v3.8.2\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-6rrfcj?file=pages%2Findex.vue\r\n\r\nNote: Issue relates to keyboard navigation! - not mouse.\r\n\r\n- Open `index` page and tab bring focus to button labelled `Goto Two`. \r\n- Hit enter key to effectively `click` button. (remember, keyboard - not mouse!)\r\n- Browser navigates to page `two`\r\n\r\nNotice the header suggests that the function `handleNext` has been called. This suggest that the `@keyup` event has fired on the `input` control on page `two` as `handleNext` is the function handling of that event. I can't think why this should be expected behaviour. Almost as if the `keyup` event from pressing the button on the `index` page is being seen by page `two` when the `focus()` call is made?! \r\n\r\nOpen the browser devtools to see console.log messages also indicating that `handleNext` has been called.\r\n\r\nAlso, to add additional context/relevant to help diagnose the error. In the script for `two.vue` there is another option (2) that can be uncommented and option (1) commented out. This only calls `focus()` after a delay. With this in place the potential bug doesn't happen.\r\n\r\n### Describe the bug\r\n\r\nI'm seeing what I think maybe a bug when navigating to a page that combines and `input` control with an associated `@keyup` handler that is also focused on page load via `onMounted` lifecycle event.\r\n\r\nFollow the reproduction above and also the effect of delaying the call to `focus()` on the `input` control.\r\n\r\n\r\n### Additional context\r\n\r\nChanging the event type on the `input` field from `@keyup` to `@keydown` also avoids the issue.\r\n\r\n### Logs\r\n\r\n_No response_",[3243,3246],{"name":3244,"color":3245},"3.x","29bc7f",{"name":3247,"color":3248},"pending triage","E99695",24434,"Unexpected @keyup triggering on focused input field when navigated to via keyboard \"click\"","2023-11-28T14:35:12Z","https://github.com/nuxt/nuxt/issues/24434",0.7149162,{"description":3255,"labels":3256,"number":3263,"owner":3147,"repository":3147,"state":3177,"title":3264,"updated_at":3265,"url":3266,"score":3267},"### Version\r\n```>= 1.0-rc0```\r\n\r\n### Reproduction links\r\nhttps://glitch.com/edit/#!/nuxt-rc0\r\nhttps://nuxt-rc0.glitch.me/\r\nhttps://nuxt-rc0.glitch.me/about\r\n\r\n### Steps to reproduce\r\nLoad the page above, and start typing into the search field. The input element is set to trigger an update of the query string on keypress.\r\n\r\n### What is expected?\r\nYou should be able to continue typing after the first character, and the query string url should continue updating with what you type. \r\n\r\n### What is actually happening?\r\nAfter every keypress, the form field loses focus and you have to click inside again to be able to type the next character.\r\n\r\nAdditionally, if the typing is done on the about page in the above demo, then it also scrolls to the top of the page after each keypress, despite the custom scroll Behaviour disabling that.\r\n\r\n### Extra Information\r\nI noticed this change in behavior when I upgraded from 1.0.0-alpha.4 to 1.0.0-rc3, but after checking the previous versions it seems to have started in 1.0.0-rc0.\r\n\r\nLinks to a glitch to see a working previous version\r\nhttps://glitch.com/edit/#!/nuxt-alpha4\r\nhttps://nuxt-alpha4.glitch.me/\r\nhttps://nuxt-alpha4.glitch.me/about\r\n\r\nTo rule out changes upstream in vue router causing this, I created a jsfiddle using version 2.7.0 of vue-router (same as nuxt 1.0.0-rc3 uses). The behaviour *does not* exist in that test:\r\nhttps://jsfiddle.net/benosman/octu95ra/\r\n\r\nNote: This issue has been rewritten, hopefully to make it clearer to understand what the problem is.\r\n\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1112\">#c1112\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3257,3260],{"name":3258,"color":3259},"question","cc317c",{"name":3261,"color":3262},"2.x","d4c5f9",1255,"Pages are fully re-rendered when just query string changes - focus on active element lost","2023-01-18T15:41:00Z","https://github.com/nuxt/nuxt/issues/1255",0.7273107,["Reactive",3269],{},["Set"],["ShallowReactive",3272],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f3ho01Cq_Qn4yayATzMypJHDY8P2Jk_izBA7cFaYNj_8":-1},"/nuxt/ui/4879"]