\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```",[3197,3198,3199,3200,3201],{"name":3140,"color":3141},{"name":3143,"color":3144},{"name":3146,"color":3147},{"name":3187,"color":3188},{"name":3202,"color":3188},"stale",3933,"SelectMenu's autofocus doesn't work inside Modal","2025-08-12T02:12:37Z","https://github.com/nuxt/ui/issues/3933",0.6351711,{"description":3209,"labels":3210,"number":3213,"owner":3149,"repository":3150,"state":3173,"title":3214,"updated_at":3215,"url":3216,"score":3217},"### Environment\n\n- Operating System: Linux\n- Node Version: v20.12.0\n- Nuxt Version: -\n- CLI Version: 3.27.0\n- Nitro Version: -\n- Package Manager: pnpm@8.15.6\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nVue, Nuxt probably too\n\n### Version\n\nv3.3.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/autumn-fog-8l524s\n\n### Description\n\nWhen nesting `Select` or `InputMenu` inside a `FormField`, clicking the label does not focus/open the input. Interestingly, it does work as expected for `SelectMenu`. See reproduction for examples.\n",[3211,3212],{"name":3140,"color":3141},{"name":3143,"color":3144},4690,"[Select/InputMenu]: Focus via label not working inside FormField","2025-08-14T10:22:07Z","https://github.com/nuxt/ui/issues/4690",0.6463542,{"description":3219,"labels":3220,"number":3226,"owner":3149,"repository":3150,"state":3173,"title":3227,"updated_at":3228,"url":3229,"score":3230},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.1.0`\n- Nuxt Version: `3.16.2`\n- CLI Version: `3.24.0`\n- Nitro Version: `2.11.8`\n- Package Manager: `yarn@4.7.0`\n- Builder: `-`\n- User Config: `modules`, `ssr`, `components`, `app`, `css`, `runtimeConfig`, `compatibilityDate`, `nitro`, `vite`, `eslint`\n- Runtime Modules: `@pinia/nuxt@0.10.1`, `pinia-plugin-persistedstate/nuxt@4.2.0`, `@nuxt/ui@3.0.2`, `dayjs-nuxt@2.1.11`, `@nuxt/eslint@1.3.0`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/sandbox/festive-feather-mzq49q\n\nIn the second select (which is wrapped in a form tag), don't select anything, and click save to submit the form.\n\nIt should show the browser \"this input is required\" tooltip.\n\n### Description\n\nI can't really understand why/how this happens. Sometimes, the `required` prop on a Select component will not prevent the form to be submitted. But sometimes it's working fine.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3221,3222,3223,3224,3225],{"name":3140,"color":3141},{"name":3143,"color":3144},{"name":3146,"color":3147},{"name":3187,"color":3188},{"name":3202,"color":3188},3882,"Select required sometimes not working","2025-08-12T02:12:49Z","https://github.com/nuxt/ui/issues/3882",0.6491569,{"description":3232,"labels":3233,"number":3237,"owner":3149,"repository":3150,"state":3173,"title":3238,"updated_at":3239,"url":3240,"score":3241},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.13.1\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.8\n- Package Manager: yarn@4.8.1\n- Builder: -\n- User Config: compatibilityDate, imports, components, devtools, modules, css, fonts, ui\n- Runtime Modules: @nuxt/eslint@1.2.0, @nuxt/fonts@0.11.0, @nuxt/image@1.10.0, @nuxt/test-utils@3.17.2, @nuxt/ui@3.0.2\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.2\n\n### Reproduction\n\nhttps://github.com/nuxt/ui/blob/v3/src/theme/button.ts\n\n### Description\n\nSome button variants have `focus:outline-none` by default, so it's impossible to unset it. It's reduces accessibility\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3234,3235,3236],{"name":3140,"color":3141},{"name":3143,"color":3144},{"name":3146,"color":3147},3739,"Unable unset focus outline","2025-05-10T17:04:44Z","https://github.com/nuxt/ui/issues/3739",0.6673585,{"description":3243,"labels":3244,"number":3251,"owner":3149,"repository":3149,"state":3173,"title":3252,"updated_at":3253,"url":3254,"score":3255},"### 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_",[3245,3248],{"name":3246,"color":3247},"3.x","29bc7f",{"name":3249,"color":3250},"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.67281896,{"description":3257,"labels":3258,"number":3262,"owner":3149,"repository":3150,"state":3173,"title":3263,"updated_at":3264,"url":3265,"score":3266},"### Environment\n\n- Operating System: Linux\n- Node Version: v20.12.0\n- Nuxt Version: 3.17.3\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: pnpm@8.15.6\n- Builder: -\n- User Config: modules, devtools, compatibilityDate, future, css\n- Runtime Modules: @nuxt/ui@3.1.1\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.2.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/pensive-spence-mtw49s\n\n### Description\n\nThe `title` attribute works. But Typescript is not happy.\n\n\u003Cimg width=\"1300\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/37005c53-d229-476c-b287-1578fc517c64\" />\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3259,3260,3261],{"name":3140,"color":3141},{"name":3143,"color":3144},{"name":3146,"color":3147},4407,"SelectInput search-input props has typescript errors with native input attributes","2025-07-12T12:31:08Z","https://github.com/nuxt/ui/issues/4407",0.67504185,["Reactive",3268],{},["Set"],["ShallowReactive",3271],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fdCRrgUwlA50ipCVW87DDRcpj7L82g--qx8vV1S42qd8":-1},"/nuxt/ui/3791"]