\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```",[3075,3078],{"name":3076,"color":3077},"pending triage","E99695",{"name":3051,"color":3079},"FBCA04",30185,"Page refresh bug","2025-02-03T14:25:51Z","https://github.com/nuxt/nuxt/issues/30185",0.70217896,{"description":3086,"labels":3087,"number":3093,"owner":3028,"repository":3028,"state":3056,"title":3094,"updated_at":3095,"url":3096,"score":3097},"### 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>",[3088,3089,3090],{"name":3076,"color":3077},{"name":3051,"color":3079},{"name":3091,"color":3092},"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":3099,"labels":3100,"number":3107,"owner":3028,"repository":3029,"state":3056,"title":3108,"updated_at":3109,"url":3110,"score":3111},"### 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```",[3101,3102,3103,3106],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3104,"color":3105},"nuxt/ui-pro","00dc82",{"name":3025,"color":3026},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":3113,"labels":3114,"number":3119,"owner":3028,"repository":3028,"state":3056,"title":3120,"updated_at":3121,"url":3122,"score":3123},"### 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_",[3115,3118],{"name":3116,"color":3117},"3.x","29bc7f",{"name":3076,"color":3077},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,{"description":3125,"labels":3126,"number":3129,"owner":3028,"repository":3028,"state":3056,"title":3130,"updated_at":3131,"url":3132,"score":3133},"### Environment\r\n\r\n- Operating System: windows10\r\n- Node Version: v20.10.0\r\n- Nuxt Version: 3.8.2\r\n- vue: 3.3.10\r\n- vue-router: 4.2.5\r\n- Package Manager: npm@10.2.3\r\n\r\n### Reproduction\r\n\r\n复现地址:https://stackblitz.com/edit/github-hi9xzq?file=app.vue,pages%2Findex.vue,pages%2Ftest.vue\r\n\r\n### Describe the bug\r\n\r\n### 这个Index组件beforeRouteEnter钩子函数在浏览器刷新页面的时候未执行nuxt传入的回调函数,正常的nuxt-link组件跳转就会正常执行。\r\n```\r\n\r\n\u003Cscript lang=\"tsx\">\r\nexport default defineComponent({\r\n name: 'Index',\r\n beforeRouteEnter(to, form, next) {\r\n console.log({ to, form, next })\r\n return next(vm => {\r\n console.log({ vm })\r\n })\r\n },\r\n setup() {\r\n return () => (\r\n \u003Cdiv>\r\n \u003Cdiv>Index\u003C/div>\r\n \u003Cnuxt-link to=\"/test\">Text\u003C/nuxt-link>\r\n \u003C/div>\r\n )\r\n }\r\n})\r\n\u003C/script>\r\n\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_\n```[tasklist]\n### Tasks\n```\n",[3127,3128],{"name":3116,"color":3117},{"name":3076,"color":3077},24989,"nuxt3 的tsx组件中beforeRouteEnter感觉有怪异的情况","2024-01-02T04:51:38Z","https://github.com/nuxt/nuxt/issues/24989",0.70519805,{"description":3135,"labels":3136,"number":3139,"owner":3028,"repository":3028,"state":3056,"title":3140,"updated_at":3141,"url":3142,"score":3143},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.8.2\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: devtools, vite\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-s3ebia?file=app.vue,components%2FFullscreenBackground.vue\r\n\r\n### Describe the bug\r\n\r\nI was making a background for a modal component when I noticed a strange behaviour with the `\u003CTransition />` component, specifically when the `appear` prop is set.\r\n\r\nIt seems that the click event listener on an element inside `\u003CTransition appear>` isn't being properly handled.\r\nSteps to reproduce:\r\n1. open the reproduction\r\n2. click on the semi-transparent fullscreen div\r\n3. *nothing happens* even though it should have set its visibility to `false`\r\n\r\n1. remove `appear` from the `\u003CTransition>` component in `FullscreenBackground.vue`\r\n2. repeat the same steps & now the click is properly handled\r\n\r\n### Additional context\r\n\r\nI've tried and I couldn't reproduce the same issue in Vue, so I assume it could be a bug in Nuxt.\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3137,3138],{"name":3116,"color":3117},{"name":3076,"color":3077},24754,"`\u003CTransition appear>` breaks click event listener","2023-12-15T10:09:43Z","https://github.com/nuxt/nuxt/issues/24754",0.7073552,["Reactive",3145],{},["Set"],["ShallowReactive",3148],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fSUwklFcFCb8V7f4RPmgSd8wYkWPkufUk0reqLOeXIsk":-1},"/nuxt/ui/4612"]