\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>",[2982,2985],{"name":2983,"color":2984},"documentation","5319e7",{"name":2952,"color":2953},1715,"Mix of slot and nuxt-child breaks everything","2023-01-18T15:42:10Z","https://github.com/nuxt/nuxt/issues/1715",0.7341991,{"description":2992,"labels":2993,"number":2996,"owner":2912,"repository":2997,"state":2931,"title":2998,"updated_at":2999,"url":3000,"score":3001},"Since the ui lib now uses the new version of Nuxt Color Mode, we'll need to add a `ThemeSelect` component https://github.com/docusgen/docus.com/blob/dev/components/atoms/ThemeSelect.vue and add it in the dropdown like on Docus: \n\n",[2994],{"name":2949,"color":2995},"1ad6ff",65,"nuxt.com","Theme selector","2023-02-15T12:30:35Z","https://github.com/nuxt/nuxt.com/issues/65",0.7359582,{"description":3003,"labels":3004,"number":3008,"owner":2912,"repository":2913,"state":2931,"title":3009,"updated_at":3010,"url":3011,"score":3012},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v18.20.8`\n- Nuxt Version: `-`\n- CLI Version: `3.25.1`\n- Nitro Version: `-`\n- Package Manager: `npm@10.8.2`\n- Builder: `-`\n- User Config: `-`\n- Runtime Modules: `-`\n- Build Modules: `-`\n\n### Is this bug related to Nuxt or Vue?\n\nVue\n\n### Version\n\nv3.1.3\n\n### Reproduction\n\nhttps://codesandbox.io/p/sandbox/modal-close-not-working-kc99r3\n\n### Description\n\nThe scoped slots `content`, `header`, `body` and `footer` in UModal are supposed to receive an object containing a close-method, as per [the docs](https://ui.nuxt.com/components/modal#slots). They do not; only an empty object is received. Due to this, the Cancel-button from the [footer-example](https://ui.nuxt.com/components/modal#with-footer-slot) in the docs does not work. Inexplicably, the example in the docs works 🤔\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3005,3006,3007],{"name":2903,"color":2904},{"name":2906,"color":2907},{"name":2909,"color":2910},4266,"Modal content, header, body and footer slots not receiving the close method","2025-06-01T06:07:09Z","https://github.com/nuxt/ui/issues/4266",0.7368391,{"description":3014,"labels":3015,"number":3020,"owner":2912,"repository":2913,"state":2931,"title":3021,"updated_at":3022,"url":3023,"score":3024},"### Environment\n\n- Operating System: Darwin\r\n- Node Version: v22.4.0\r\n- Nuxt Version: 3.12.4\r\n- CLI Version: 3.13.1\r\n- Nitro Version: -\r\n- Package Manager: pnpm@9.4.0\r\n- Builder: -\r\n- User Config: compatibilityDate, devtools, future, experimental, app, site, sitemap, routeRules, css, colorMode, runtimeConfig, modules, postcss, typescript\r\n- Runtime Modules: nuxt-headlessui@1.2.0, @nuxt/eslint@0.3.13, @nuxt/ui@2.18.4, @pinia/nuxt@0.5.4, @pinia-plugin-persistedstate/nuxt@1.2.1, @nuxt/scripts@0.8.4, nuxt-anchorscroll@1.0.3, @nuxtjs/seo@2.0.0-rc.21\r\n- Build Modules: -\n\n### Version\n\nv2.18.4\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/command-palette#usage\n\n### Description\n\nOn mobile devices, when the modal is positioned at the bottom of the screen, the Command Palette becomes obscured by the virtual keyboard. This issue occurs when the Command Palette contains fewer than 6 elements or none at all, making it completely inaccessible for users.\r\n\r\nThe issue can be reproduced on the official component page: \r\n[https://ui.nuxt.com/components/command-palette](https://ui.nuxt.com/components/command-palette)\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3016,3017,3018,3019],{"name":2903,"color":2904},{"name":2909,"color":2910},{"name":2926,"color":2927},{"name":2929,"color":2927},2157,"Command Palette appears behind virtual keyboard when inside Modal on mobile devices","2025-06-18T09:06:08Z","https://github.com/nuxt/ui/issues/2157",0.7375054,["Reactive",3026],{},["Set"],["ShallowReactive",3029],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f2Ld9pvhsULdKki0UKGd6GXWln7xUcBcJhSl76fgFggQ":-1},"/nuxt/ui/3078"]