\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```",[3184,3185,3186,3187,3190],{"name":3140,"color":3141},{"name":3143,"color":3144},{"name":3146,"color":3147},{"name":3188,"color":3189},"closed-by-bot","ededed",{"name":3191,"color":3189},"stale",3933,"SelectMenu's autofocus doesn't work inside Modal","2025-08-12T02:12:37Z","https://github.com/nuxt/ui/issues/3933",0.6910434,{"description":3198,"labels":3199,"number":3203,"owner":3149,"repository":3150,"state":3166,"title":3204,"updated_at":3205,"url":3206,"score":3207},"### 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```",[3200,3201,3202],{"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.69805557,{"description":3209,"labels":3210,"number":3216,"owner":3149,"repository":3149,"state":3166,"title":3217,"updated_at":3218,"url":3219,"score":3220},"### Environment\n\n*package.json*\n```js\n{\n \"name\": \"nuxt-app\",\n \"private\": true,\n \"type\": \"module\",\n \"scripts\": {\n \"build\": \"nuxt build\",\n \"dev\": \"nuxt dev\",\n \"generate\": \"nuxt generate\",\n \"preview\": \"nuxt preview\",\n \"postinstall\": \"nuxt prepare\"\n },\n \"dependencies\": {\n \"@prisma/nuxt\": \"^0.1.2\",\n \"@vueuse/core\": \"^12.0.0\",\n \"@vueuse/nuxt\": \"^12.0.0\",\n \"nuxt\": \"^3.14.1592\",\n \"vue\": \"latest\",\n \"vue-router\": \"latest\"\n },\n \"devDependencies\": {\n \"@nuxt/devtools\": \"npm:@nuxt/devtools-edge@latest\",\n \"@nuxtjs/tailwindcss\": \"^6.12.2\",\n \"@prisma/client\": \"^6.0.1\",\n \"prisma\": \"^6.0.1\"\n }\n}\n\n```\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-uquybs?file=nuxt.config.ts,app.vue\n\n### Describe the bug\n\nI have this code that should submit a form but I added `submit.prevent=\"handleSubmit()\"` so this should stop from refreshing.\n\nI tried to reproduce it on stackblitz however everything is working there (including the devtools) but on my local upon clicking create button the page refreshes.\n\n\n\n```html\n\u003Ctemplate>\n\u003Cform @submit.prevent=\"handleSubmit()\" class=\"w-full\">\n\t\u003Cdiv class=\"mb-4\">\n\t\t\u003Cinput\n\t\t\tv-model=\"form.email\"\n\t\t\ttype=\"email\"\n\t\t\tid=\"email\"\n\t\t\tclass=\"w-full p-3 border border-gray-300 rounded mt-1\"\n\t\t\tplaceholder=\"Email address\"\n\t\t/>\n\t\u003C/div>\n\t\u003Cdiv class=\"mb-6\">\n\t\t\u003Cinput\n\t\t\tv-model=\"form.password\"\n\t\t\ttype=\"password\"\n\t\t\tid=\"password\"\n\t\t\tclass=\"w-full p-3 border border-gray-300 rounded mt-1\"\n\t\t\tplaceholder=\"Password\"\n\t\t/>\n\t\u003C/div>\n\t\u003Cdiv class=\"mb-6\">\n\t\t\u003Cinput\n\t\t\tv-model=\"form.confirm_password\"\n\t\t\ttype=\"confirm_password\"\n\t\t\tid=\"confirm_password\"\n\t\t\tclass=\"w-full p-3 border border-gray-300 rounded mt-1\"\n\t\t\tplaceholder=\"Password Confirmation\"\n\t\t/>\n\t\u003C/div>\n\t\u003Cbutton\n\t\ttype=\"submit\"\n\t\tclass=\"w-full bg-blue-600 text-white p-3 rounded hover:bg-blue-700\"\n\t>\n\t\tCreate\n\t\u003C/button>\n\u003C/form>\n\u003C/template>\n\u003Cscript setup>\nconst handleSubmit = async () => {\n\t\n\tif (form.value.password !== form.value.confirm_password) {\n\t\tconsole.log(\"Passwords do not match\");\n\t\talert(\"Passwords do not match\");\n\t\treturn;\n\t}\n\n\tconsole.log(form.value);\n};\n...\n```\n\nhttps://github.com/user-attachments/assets/18ea3431-cadb-4613-a2a3-4703755f2f91\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3211,3214],{"name":3212,"color":3213},"pending triage","E99695",{"name":3161,"color":3215},"FBCA04",30185,"Page refresh bug","2025-02-03T14:25:51Z","https://github.com/nuxt/nuxt/issues/30185",0.70217896,{"description":3222,"labels":3223,"number":3229,"owner":3149,"repository":3149,"state":3166,"title":3230,"updated_at":3231,"url":3232,"score":3233},"### Environment\n\nNuxt project info: 10:52:59 AM\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.9.0\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-d9qil3\n\nBe sure to open in full page, and open the dev console\n\n### Describe the bug\n\n`\u003CSomeComponent>.server.vue` actually still works, but if it contains a **selectiveClient** / `nuxt-client` element, this part is now broken, until you refresh or navigate to another page, using links and not the browser buttons (well refresh does work)\n\nWhether or not the server component contains a **selectiveClient** is irrelevant to the error message in the console, it will still throw that error\n\nHowever if it does contain a **selectiveClient**, then that part of the server component, is now broken\n\n### Additional context\n\nWhen using normal links (either a href, or \u003CNuxtLink>) this does not happen\n\nIt only happens when hitting the back button in the browser (or shortcut on mouse)\n\nEDIT:\nActually it does happen with NuxtLink's, the href is simply reloading the whole page, that's why it's not happening there\n\n### Logs\n\nruntime-core.esm-bundler.js?v=c0e84aa4:50 [Vue warn]: Failed to locate Teleport target with selector \"div[data-island-uid='1'][data-island-component=\"CounterButton-hb1RAsRv3M\"]\". Note the target element must exist before the component is mounted - i.e. the target cannot be rendered by the component itself, and ideally should be outside of the entire Vue component tree. \n at \u003CNuxtIsland name=\"HelloIsland\" > \n at \u003CIndex onVnodeUnmounted=fn\u003ConVnodeUnmounted> ref=Ref\u003C Proxy(Object) {__v_skip: true} > > \n at \u003CAnonymous key=\"/\" vnode= {__v_isVNode: true, __v_skip: true, type: {…}, props: {…}, key: null, …} route= {fullPath: '/', path: '/', query: {…}, hash: '', name: 'index', …} ... > \n at \u003CRouterView name=undefined route=undefined > \n at \u003CNuxtPage> \n at \u003CSideMenu ref=Ref\u003C Proxy(Object) {…} > > \n at \u003CLayoutLoader key=\"side-menu\" layoutProps= {ref: RefImpl} name=\"side-menu\" > \n at \u003CNuxtLayoutProvider layoutProps= {ref: RefImpl} key=\"side-menu\" name=\"side-menu\" ... > \n at \u003CNuxtLayout> \n at \u003CApp key=4 > \n at \u003CNuxtRoot>",[3224,3225,3226],{"name":3212,"color":3213},{"name":3161,"color":3215},{"name":3227,"color":3228},"server components","839413",29345,"NuxtIsland: Failed to locate Teleport target with selector","2024-12-09T10:35:39Z","https://github.com/nuxt/nuxt/issues/29345",0.7025403,{"description":3235,"labels":3236,"number":3244,"owner":3149,"repository":3150,"state":3166,"title":3245,"updated_at":3246,"url":3247,"score":3248},"### Environment\n\nOperating System: Windows 11\nNode Version: v22.14.0\nNuxt Version: 3.17.4\nNitro Version: 2.11.12\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.3\n\n### Description\n\nHi,\nWhen I use the mouseenter and mouseleave or mouseover and mouseout events, the following error appears and the events don't work:\n\n\"[Vue warn]: Extraneous non-emits event listeners (mouseenter, mouseleave) were passed to component but could not be automatically inherited because component renders fragment or text root nodes. If the listener is intended to be a component custom event listener only, declare it using the emits option.\"\n\nWhat should I do? Can you help me?\n",[3237,3238,3239,3240,3243],{"name":3140,"color":3141},{"name":3161,"color":3162},{"name":3143,"color":3144},{"name":3241,"color":3242},"nuxt/ui-pro","00dc82",{"name":3188,"color":3189},4268,"Extraneous non-emits event listeners (mouseenter, mouseleave) on UDashboardSidebar component","2025-08-15T02:16:25Z","https://github.com/nuxt/ui/issues/4268",0.7034507,{"description":3250,"labels":3251,"number":3256,"owner":3149,"repository":3150,"state":3166,"title":3257,"updated_at":3258,"url":3259,"score":3260},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v22.14.0\n- Nuxt Version: 3.16.2\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.9\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: modules, devtools, css, future, compatibilityDate, eslint, nitro\n- Runtime Modules: @nuxt/eslint@1.3.0, @nuxt/ui-pro@3.0.2, @vueuse/nuxt@13.1.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nui pro v3.0.2\n\n### Reproduction\n\n1. add a `\u003CUPageCard spotlight>`\n2. hover over all of the corners\n3. one of them wont work\n\n### Description\n\nwhen a UPageCard component has spotlight turned on, one of the corners will never work. in my projects it was always the top left one.\n\n### Additional context\n\nin both images the cursor is around 15px from the actual corner\n\n\n\n\n### Logs\n\n```shell-script\n\n```",[3252,3253,3254,3255],{"name":3140,"color":3141},{"name":3143,"color":3144},{"name":3241,"color":3242},{"name":3146,"color":3147},4040,"UPageCard spotlight not working in one of the corners","2025-05-07T08:40:22Z","https://github.com/nuxt/ui/issues/4040",0.70381653,{"description":3262,"labels":3263,"number":3268,"owner":3149,"repository":3149,"state":3166,"title":3269,"updated_at":3270,"url":3271,"score":3272},"### 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_",[3264,3267],{"name":3265,"color":3266},"3.x","29bc7f",{"name":3212,"color":3213},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.7045571,["Reactive",3274],{},["Set"],["ShallowReactive",3277],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fSUwklFcFCb8V7f4RPmgSd8wYkWPkufUk0reqLOeXIsk":-1},"/nuxt/ui/4612"]