\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3092,3093,3094],{"name":3019,"color":3020},{"name":3036,"color":3037},{"name":3039,"color":3040},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,{"description":3101,"labels":3102,"number":3108,"owner":3025,"repository":3042,"state":3059,"title":3109,"updated_at":3110,"url":3111,"score":3112},"### Environment\n\n- Operating System: Darwin\n- Node Version: v18.20.3\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.17.2\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.8.2\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/eslint@0.6.2, @nuxt/fonts@0.10.3, @nuxt/ui@2.20.0, @vueuse/nuxt@12.0.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.13.2\n\n### Reproduction\n\n1. Use this template: https://github.com/nuxt-ui-pro/dashboard\n2. Run the app (npm run dev) (or run the demo: https://dashboard-template.nuxt.dev/)\n3. Open devtools and toggle device toolbar\n4. Click on the menu icon and then the nuxt text on the top. \n5. It is buggy because the hover mode is not taking into account the touch device input.\n\n\n\n\n### Description\n\nI use the template from https://github.com/nuxt-ui-pro/dashboard and tested it on mobile.\nThe component UDropdown has a mode of 'hover'. This however breaks the interaction on mobile/touch devices.\n\n\u003CUDropdown v-slot=\"{ open }\" mode=\"hover\" :items=\"[teams, actions]\" class=\"w-full\" :ui=\"{ width: 'w-full' }\"\n :popper=\"{ strategy: 'absolute' }\">\n\nThis is reproduced in the devtools using the mobile emulator, as well as your own device (ios).\n\n### Additional context\n\nI believe this to be a bug since an example should be working properly on all devices without workarounds.\n\n### Logs\n\n```shell-script\n\n```",[3103,3104,3105,3106],{"name":3019,"color":3020},{"name":3039,"color":3040},{"name":3056,"color":3057},{"name":3107,"color":3057},"stale",2989,"Dropdown with mode=\"hover\" breaks interaction on touch device","2025-06-18T09:05:08Z","https://github.com/nuxt/ui/issues/2989",0.67519844,{"description":3114,"labels":3115,"number":3118,"owner":3025,"repository":3042,"state":3059,"title":3119,"updated_at":3120,"url":3121,"score":3122},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.14.0\n- Nuxt Version: 3.17.1\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.11\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: app, build, colorMode, compatibilityDate, debug, devtools, fonts, future, hooks, i18n, icon, imports, modules, nitro, routeRules, runtimeConfig, security, ssr, sourcemap, css, telemetry, vite\n- Runtime Modules: @nuxt/eslint@1.3.0, @pinia/nuxt@0.11.0, @vueuse/nuxt@13.1.0, @nuxtjs/i18n@9.5.3, nuxt-security@2.2.0, @nuxt/ui@3.1.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/epic-smoke-95wysw?file=%2Fapp%2Fpages%2Findex.vue\n\n### Description\n\nUsing the `@update:model-value` event handler produces type errors with the Select component, starting from nuxt-ui v3.1.0 (v3.0.2 works fine).\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nType 'boolean | AcceptableValue | undefined' is not assignable to type '\"yes\" | \"no\"'.\n Type 'undefined' is not assignable to type '\"yes\" | \"no\"'.ts-plugin(2322)\n```",[3116,3117],{"name":3019,"color":3020},{"name":3036,"color":3037},4019,"Type Issue with Select Component","2025-04-29T15:39:56Z","https://github.com/nuxt/ui/issues/4019",0.6758617,{"description":3124,"labels":3125,"number":3130,"owner":3025,"repository":3042,"state":3059,"title":3131,"updated_at":3132,"url":3133,"score":3134},"### Environment\n\n- Operating System: Linux\n- Node Version: v20.9.0\n- Nuxt Version: 3.15.3\n- CLI Version: 3.20.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.13.1\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, css\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.12, @vee-validate/nuxt@4.15.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.12\n\n### Reproduction\n\nhttps://stackblitz.com/~/github.com/arpadgabor/nuxt-ui-3-bug\n\nIn case the above link does not work, here is the repo: https://github.com/arpadgabor/nuxt-ui-3-bug\n\n### Description\n\nWhen using the Select and SelectMenu components with vee-validate, especially when there are multiple fields involved, there is a very weird behaviour. Selection does not work correctly, cannot close the dropdown, etc. I've added a recording as well (I keep clicking outside and on the menu options).\n\nhttps://github.com/user-attachments/assets/bc8aa97c-377c-4f57-ab7d-55929f30d97c\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3126,3127,3128,3129],{"name":3019,"color":3020},{"name":3036,"color":3037},{"name":3039,"color":3040},{"name":3107,"color":3057},3194,"[Select] Buggy behaviour of Select fields when used with vee-validate","2025-06-12T15:32:10Z","https://github.com/nuxt/ui/issues/3194",0.6774886,{"description":3136,"labels":3137,"number":3141,"owner":3025,"repository":3042,"state":3059,"title":3142,"updated_at":3143,"url":3144,"score":3145},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.13.0`\n- Nuxt Version: `3.16.2`\n- CLI Version: `3.24.1`\n- Nitro Version: `2.11.9`\n- Package Manager: `pnpm@10.8.1`\n- Builder: `-`\n- User Config: `modules`, `devtools`, `css`, `site`, `future`, `compatibilityDate`, `echarts`, `eslint`, `fonts`, `icon`, `sitemap`\n- Runtime Modules: `@nuxtjs/sitemap@7.2.10`, `@nuxt/content@3.4.0`, `@nuxt/eslint@1.3.0`, `@nuxt/ui-pro@3.0.2`, `@vueuse/nuxt@13.1.0`, `nuxt-echarts@0.3.0`\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://codesandbox.io/p/devbox/peaceful-elbakyan-3ddsxd\n\n### Description\n\nMy understanding is that the onSelect event of SelectMenu should be consistent with the DropdownMenu component, but in reality, it is not.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3138,3139,3140],{"name":3019,"color":3020},{"name":3036,"color":3037},{"name":3039,"color":3040},3978,"The onSelect event of the SelectMenu component was not triggered","2025-05-05T15:20:55Z","https://github.com/nuxt/ui/issues/3978",0.67804146,["Reactive",3147],{},["Set"],["ShallowReactive",3150],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fdCRrgUwlA50ipCVW87DDRcpj7L82g--qx8vV1S42qd8":-1},"/nuxt/ui/3791"]