\n\nI believe this is an issue with Nuxt UI and not FormKit because it used to work fine on the previous version.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nindex.vue:17 [Vue warn]: Unhandled error during execution of mounted hook \n at \u003CDialogTrigger key=0 as-child=\"\" class=\"\" > \n at \u003CDialogRoot modal=true open=true onAfter:leave=fn ... > \n at \u003CUModal close= {onClick: ƒ} title=\"This modal was opened programmatically 0 times\" open=true ... > \n at \u003CModalExample key= Symbol(useOverlay) ref_for=true count=0 ... > \n at \u003CUOverlayProvider > \n at \u003CTooltipProvider > \n at \u003CConfigProvider use-id=fn\u003Cuse-id> dir=undefined locale=undefined > \n at \u003CApp > \n at \u003CApp key=4 > \n at \u003CNuxtRoot>\nwarn$1 @ runtime-core.esm-bundler.js?v=fb91d406:50\nlogError @ runtime-core.esm-bundler.js?v=fb91d406:261\nhandleError @ runtime-core.esm-bundler.js?v=fb91d406:253\ncallWithErrorHandling @ runtime-core.esm-bundler.js?v=fb91d406:199\ncallWithAsyncErrorHandling @ runtime-core.esm-bundler.js?v=fb91d406:204\nhook.__weh.hook.__weh @ runtime-core.esm-bundler.js?v=fb91d406:2842\nflushPostFlushCbs @ runtime-core.esm-bundler.js?v=fb91d406:382\nflushJobs @ runtime-core.esm-bundler.js?v=fb91d406:424\nPromise.then\nqueueFlush @ runtime-core.esm-bundler.js?v=fb91d406:319\nqueueJob @ runtime-core.esm-bundler.js?v=fb91d406:314\neffect2.scheduler @ runtime-core.esm-bundler.js?v=fb91d406:5499\ntrigger @ reactivity.esm-bundler.js?v=fb91d406:235\nendBatch @ reactivity.esm-bundler.js?v=fb91d406:293\ntrigger @ reactivity.esm-bundler.js?v=fb91d406:693\nset @ reactivity.esm-bundler.js?v=fb91d406:974\nopen @ useOverlay.js?v=fb91d406:29\nopen @ useOverlay.js?v=fb91d406:18\nopen @ index.vue:17\n(anonymous) @ Button.vue:80\nonClickWrapper @ Button.vue:80\nonClickWrapper @ LinkBase.vue:30\ncallWithErrorHandling @ runtime-core.esm-bundler.js?v=fb91d406:197\ncallWithAsyncErrorHandling @ runtime-core.esm-bundler.js?v=fb91d406:204\ninvoker @ runtime-dom.esm-bundler.js?v=fb91d406:720\nuseForwardExpose.js?v=fb91d406:8 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'nodeName')\n at ComputedRefImpl.fn (useForwardExpose.js?v=fb91d406:8:64)\n at refreshComputed (reactivity.esm-bundler.js?v=fb91d406:361:29)\n at get value (reactivity.esm-bundler.js?v=fb91d406:1567:5)\n at DialogTrigger.js?v=fb91d406:19:57\n at runtime-core.esm-bundler.js?v=fb91d406:2862:40\n at callWithErrorHandling (runtime-core.esm-bundler.js?v=fb91d406:197:19)\n at callWithAsyncErrorHandling (runtime-core.esm-bundler.js?v=fb91d406:204:17)\n at hook.__weh.hook.__weh (runtime-core.esm-bundler.js?v=fb91d406:2842:19)\n at flushPostFlushCbs (runtime-core.esm-bundler.js?v=fb91d406:382:28)\n at flushJobs (runtime-core.esm-bundler.js?v=fb91d406:424:5)\n```",[3170,3171,3172],{"name":3140,"color":3141},{"name":3143,"color":3144},{"name":3173,"color":3174},"triage","ffffff",4309,"UModal does not work with FormKit","2025-06-07T23:36:34Z","https://github.com/nuxt/ui/issues/4309",0.70987964,{"description":3181,"labels":3182,"number":3188,"owner":3146,"repository":3147,"state":3148,"title":3189,"updated_at":3190,"url":3191,"score":3192},"### Environment\n\nDevice: iPad Pro 18.1.1\n\n\n\n\n\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://ui.nuxt.com/\n\n### Description\n\n## Dropdown-Menu\n\nhttps://ui3.nuxt.dev/components/dropdown-menu#content\n\n- Pen-clicking an item within the dropdown, no matter the level, does not work\n\nOther components, like `ColorModeSelect` and `LocaleSelect` work.\n\n## Modals\n\nhttps://ui3.nuxt.dev/components/modal#title\n\n- Pen-clicking the \"close\" button on the top right does not work.\n\n## Popover\n\nhttps://ui3.nuxt.dev/components/modal#title\n\n- Touch-clicking \"Open\" does not work\n- Pen-clicking \"Open\" does not work\n\n## ColorPicker\n\nhttps://ui3.nuxt.dev/components/color-picker#usage\n\n- Touch-clicking/dragging does scroll the whole window\n- Pen-clicking/dragging on the vertical scrollbar does scroll the whole window\n\nOther componen ts, like `Slider` does actually work fine in vertical mode.\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3183,3184,3185,3186,3187],{"name":3140,"color":3141},{"name":3143,"color":3144},{"name":3173,"color":3174},{"name":3158,"color":3159},{"name":3161,"color":3159},3291,"Defects on various components on iOS devices with pen / touch","2025-08-20T02:09:25Z","https://github.com/nuxt/ui/issues/3291",0.7110514,{"labels":3194,"number":3201,"owner":3146,"repository":3146,"state":3148,"title":3202,"updated_at":3203,"url":3204,"score":3205},[3195,3198],{"name":3196,"color":3197},"pending triage","E99695",{"name":3199,"color":3200},"2.x","d4c5f9",9849,"Class methods do not work after passing them through props","2023-01-22T15:45:05Z","https://github.com/nuxt/nuxt/issues/9849",0.712992,{"description":3207,"labels":3208,"number":3214,"owner":3146,"repository":3147,"state":3148,"title":3215,"updated_at":3216,"url":3217,"score":3218},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: 4.0.3\n- CLI Version: 3.27.0\n- Nitro Version: 2.12.4\n- Package Manager: pnpm@10.15.1\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Package\n\nv3.x\n\n### Version\n\nlatest\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/frosty-goodall-2wn4kw\n\n### Description\n\nIf we make a condition for the appearance of a slot and it is initially false, then we will never see it. This is because slots are not reactive.\n\nComponents that contain an error:\n\n- CheckboxGroup\n- DropdownMenu\n- DropdownMenuContent\n- ContextMenu\n- ChangelogVersions\n- ChatMessages\n- ChatPrompt\n- DashboardSearch\n- DashboardSearchButton\n- content/ContentSearch\n- content/ContentSearchButton\n\n### Solutions\n\nOne way to solve this is to not create a variable, but to immediately write `omit(slots, [‘...’])` in the template. This will fix the rendering error, but vue will still not show the number of available slots. ",[3209,3210,3211],{"name":3140,"color":3141},{"name":3143,"color":3144},{"name":3212,"color":3213},"p3-low","0E8A16",4947,"No re-rendering in proxySlots","2025-09-14T06:40:03Z","https://github.com/nuxt/ui/issues/4947",0.71475667,{"description":3220,"labels":3221,"number":3226,"owner":3146,"repository":3146,"state":3148,"title":3227,"updated_at":3228,"url":3229,"score":3230},"I've spent many hours to investigate the strange behavior in our large app.\r\nFinally I've found it, it seems so furious that I just have no idea what to do next with nuxt and with our templates among the whole application.\r\n\r\nAs usual, I created the separate repo with very simple code to demonstrate it: https://github.com/Kasheftin/nuxt-bug4.\r\nI'll show two bugs (alhough they may have one source).\r\n\r\nI suppose the reason is this component we use as a wrapper (everything else in the demo is hello world):\r\n\r\n```\r\n\u003Ctemplate>\r\n \u003Cdiv class=\"container\">\r\n \u003Cdiv class=\"col -menu\">\r\n \u003Cslot/>\r\n \u003C/div>\r\n \u003Cdiv class=\"col -content\">\r\n \u003Cnuxt-child/>\r\n \u003C/div>\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\nIf the user goes to the index page, we show him menu column only using the index page that looks like:\r\n\r\n```\r\n\u003Ctemplate>\r\n \u003CTwoColumns>\r\n MENU GOES HERE\r\n \u003C/TwoColumns>\r\n\u003C/template>\r\n```\r\n\r\nThen he follows the nested route and the target page placed into the nuxt-child of the wrapper.\r\n\r\n# The first bug:\r\n\r\n1. Follow the /a link. There's an input field with v-model, type anything and it appears just after the input.\r\n2. Follow /a/b link. Type something into the input field. It will work, but after every keypress nuxt show the progress bar at the top of the page like it load something. Although that's just simple inner component value update.\r\n\r\n# The second bug:\r\n\r\n3. Now follow /a/b/c link. Now only the first key press works. After that the data stops updating. It seems the component dies after the first key press. Although /b and /c are just nested nuxt-childs without javascript at all. And only the buggy progress bar at the top keeps working.\r\n\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1538\">#c1538\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3222,3225],{"name":3223,"color":3224},"documentation","5319e7",{"name":3199,"color":3200},1715,"Mix of slot and nuxt-child breaks everything","2023-01-18T15:42:10Z","https://github.com/nuxt/nuxt/issues/1715",0.7152028,{"description":3232,"labels":3233,"number":3235,"owner":3146,"repository":3146,"state":3148,"title":3236,"updated_at":3237,"url":3238,"score":3239},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.15.3\n- CLI Version: 3.20.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: compatibilityDate, devtools\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-pjcxjvhm?file=app.vue,pages/index.vue\n\n### Describe the bug\n\n1. Open the **minimal reproduction**. \n2. Open the browser **devtools**, and you will see a Vue warning: \n\n ```text\n [Vue warn]: Component inside \u003CTransition> renders non-element root node that cannot be animated.\n ```\n\nHowever, in the provided **minimal reproduction**, the `\u003CNuxtPage>` slot contains only a single root node: \n\n```vue\n\u003Ctemplate>\n \u003Cdiv>\n \u003CNuxtPage\n :transition=\"{ name: 'fade', mode: 'out-in', appear: true }\"\n #=\"{ Component }\"\n >\n \u003Ccomponent :is=\"Component\" />\n \u003C/NuxtPage>\n \u003C/div>\n\u003C/template>\n```\n\nIf the `\u003CNuxtPage>` slot is not used, the warning does not appear, and everything works as expected. \n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3234],{"name":3196,"color":3197},30806,"`\u003CNuxtPage>` slots not working with transition","2025-02-06T18:10:38Z","https://github.com/nuxt/nuxt/issues/30806",0.7166311,{"description":3241,"labels":3242,"number":3252,"owner":3146,"repository":3146,"state":3148,"title":3253,"updated_at":3254,"url":3255,"score":3256},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.9.3\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: devtools, experimental\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-issues-25423\r\n\r\n### Describe the bug\r\n\r\nUsing nested slots in a server components + `nuxt-client` breaks:\r\n\r\nExample\r\n\r\n```vue\r\n\u003C!-- ServerComp.vue -->\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CAppButton nuxt-client>\r\n \u003Cslot />\r\n \u003C/AppButton>\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\n```vue\r\n\u003C!-- App.vue -->\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CServerComp>\r\n Some slot content here\r\n \u003C/ServerComp>\r\n \u003C/div>\r\n\u003C/template>\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_",[3243,3246,3249],{"name":3244,"color":3245},"3.x","29bc7f",{"name":3247,"color":3248},"🔨 p3-minor","FBCA04",{"name":3250,"color":3251},"server components","839413",25423,"Respect named slots in server components","2024-03-06T15:26:20Z","https://github.com/nuxt/nuxt/issues/25423",0.7197181,{"description":3258,"labels":3259,"number":3262,"owner":3146,"repository":3147,"state":3148,"title":3263,"updated_at":3264,"url":3265,"score":3266},"### Environment\n\n- Operating System: Darwin\n- Node Version: v18.20.6\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: yarn@1.22.22\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.13\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/modest-agnesi-drlrh4?file=%2Fapp%2Fpages%2Findex.vue%3A24%2C24\n\n### Description\n\nWhen I close a `UDrawer` that I opened via an action from a `UDropdownMenu`, the style on my \u003Cbody> tag still contains `overflow: hidden` and `user-select: none`, which prevents interaction with the page.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3260,3261],{"name":3140,"color":3141},{"name":3143,"color":3144},3406,"User interaction lock after a Drawer/DropdownMenu","2025-02-27T20:57:27Z","https://github.com/nuxt/ui/issues/3406",0.71984977,["Reactive",3268],{},["Set"],["ShallowReactive",3271],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fO8U6jO28vt8C0qe6dRcjqjVlirTfb7fQDc_o-XOn3ZU":-1},"/nuxt/ui/4266"]