\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```",[3179,3180,3181,3182,3185],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},{"name":3183,"color":3184},"closed-by-bot","ededed",{"name":3186,"color":3184},"stale",3933,"closed","SelectMenu's autofocus doesn't work inside Modal","2025-08-12T02:12:37Z","https://github.com/nuxt/ui/issues/3933",0.703895,{"description":3194,"labels":3195,"number":3199,"owner":3147,"repository":3148,"state":3188,"title":3200,"updated_at":3201,"url":3202,"score":3203},"### Description\n\nHello.\n\nWith a modal when it opens the first button present is selected. Is there a way to change selection order or prevent it completely?\nIn exemple below the reset button is pre-selected. \n\nI could reorder buttons instead but I would like no pre-selections instead and prevent users' \"miss-click\". Thanks.\n\n```html\n \u003CUModal v-model=\"dialog\" prevent-close>\n \u003CUCard>\n \u003Cp>Reset data or continue?\u003C/p>\n\n \u003Cdiv class=\"flex justify-between\">\n \u003CUButton color=\"gray\" variant=\"ghost\" @click=\"reset\">\n Delete current data\n \u003CUIcon name=\"i-heroicons-x-mark-20-solid\" class=\"text-red-600\" />\n \u003C/UButton>\n\n \u003CUButton color=\"gray\" variant=\"ghost\" @click=\"continue\">\n Continue\n \u003CUIcon name=\"i-mdi-arrow-right-circle\" class=\"text-primary\" />\n \u003C/UButton>\n \u003C/div>\n \u003C/UCard>\n \u003C/UModal>\n```",[3196],{"name":3197,"color":3198},"question","d876e3",3187,"[V2] How to prevent button pre-selection on UModal?","2025-05-23T15:45:56Z","https://github.com/nuxt/ui/issues/3187",0.72206146,{"description":3205,"labels":3206,"number":3210,"owner":3147,"repository":3148,"state":3188,"title":3211,"updated_at":3212,"url":3213,"score":3214},"### 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_",[3207,3208,3209],{"name":3138,"color":3139},{"name":3183,"color":3184},{"name":3186,"color":3184},1932,"`UModal` preventClose doesn't allow to interact with elements","2025-06-19T02:12:17Z","https://github.com/nuxt/ui/issues/1932",0.72422814,{"description":3216,"labels":3217,"number":3224,"owner":3147,"repository":3147,"state":3188,"title":3225,"updated_at":3226,"url":3227,"score":3228},"### 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_",[3218,3221],{"name":3219,"color":3220},"3.x","29bc7f",{"name":3222,"color":3223},"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.74334574,{"description":3230,"labels":3231,"number":3235,"owner":3147,"repository":3148,"state":3188,"title":3236,"updated_at":3237,"url":3238,"score":3239},"### Environment\n\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v21.6.1\r\n- Nuxt Version: 3.10.1\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: pnpm@8.15.1\r\n- Builder: -\r\n- User Config: extends, modules, app, ui, imports, devtools\r\n- Runtime Modules: @nuxt/ui@2.13.0, @pinia/nuxt@0.5.1\r\n- Build Modules: -\r\n------------------------------\n\n### Version\n\n\"@nuxt/ui\": \"^2.13.0\"\n\n### Reproduction\n\nDescription should be clear enough.\n\n### Description\n\n\u003Cimg width=\"300\" alt=\"Screen Shot 2024-02-10 at 9 02 12 AM\" src=\"https://github.com/nuxt/ui/assets/5523014/144df6f1-3704-4b13-929c-c74cfd81aecd\">\r\n\r\n\r\nWhen a `Modal` has a `Form` inside of it, and you go on mobile, the bug happens.\r\n\r\nThe modal always goes to the bottom of the screen. When the keyboard input opens, it covers the modal. \r\n\r\nClosing the keyboard input reveals the unseen mobile modal.\r\n\r\nI would suggest moving the modal to the top, or to compensate for the keyboard dynamically and be placed therefore somewhere in the top-middle.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3232,3233,3234],{"name":3138,"color":3139},{"name":3183,"color":3184},{"name":3186,"color":3184},1346,"Modal With Form on Mobile is Covered by Keyboard Input","2025-06-19T02:12:54Z","https://github.com/nuxt/ui/issues/1346",0.75003386,{"description":3241,"labels":3242,"number":3247,"owner":3147,"repository":3148,"state":3188,"title":3248,"updated_at":3249,"url":3250,"score":3251},"### Description\n\nHi, looking at the example for the UModal, it's easy to emit a close event if someone uses the close button. But if the modal is dismissible, I don't know how to emit easily an event.\n\nIn the example there is a \"dismiss\" Button, but for me that's not the same, for sure there are workarounds possible, but an easy solution that the component is catching all kinds of close events would be really helpful. Or is there a way and I don't see it?\n\nThanks a lot in advance\n\nChristoph\n\n```\n\u003Cscript setup lang=\"ts\">\ndefineProps\u003C{\n count: number\n}>()\n\nconst emit = defineEmits\u003C{ close: [boolean] }>()\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUModal\n :close=\"{ onClick: () => emit('close', false) }\"\n :title=\"`This modal was opened programmatically ${count} times`\"\n >\n \u003Ctemplate #footer>\n \u003Cdiv class=\"flex gap-2\">\n \u003CUButton color=\"neutral\" label=\"Dismiss\" @click=\"emit('close', false)\" />\n \u003CUButton label=\"Success\" @click=\"emit('close', true)\" />\n \u003C/div>\n \u003C/template>\n \u003C/UModal>\n\u003C/template>\n\n\n```\n\n\n### Additional context\n\n_No response_",[3243,3246],{"name":3244,"color":3245},"enhancement","a2eeef",{"name":3141,"color":3142},4537,"Modal emitting close event if is dismissed","2025-07-17T10:06:09Z","https://github.com/nuxt/ui/issues/4537",0.7529034,{"description":3253,"labels":3254,"number":3257,"owner":3147,"repository":3148,"state":3188,"title":3258,"updated_at":3259,"url":3260,"score":3261},"### 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```",[3255,3256],{"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.75393534,["Reactive",3263],{},["Set"],["ShallowReactive",3266],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f0p2yGB_Oi0fzbstQerNLgzIYTlpwx4mNxWsHNfKbIb8":-1},"/nuxt/ui/3062"]