\n \u003CUKbd value=\"G\" />\n \u003C/template>\n\u003C/UInput>\n```\n\u003Cimg width=\"496\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/be2e8457-b3ac-4b70-838b-2b2b7399c091\" />\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2934,2936],{"name":2909,"color":2935},"d73a4a",{"name":2869,"color":2870},2977,"The placeholder in UInput within UModal does not display","2025-03-03T09:06:21Z","https://github.com/nuxt/ui/issues/2977",0.7416679,{"description":2943,"labels":2944,"number":2950,"owner":2875,"repository":2876,"state":2913,"title":2951,"updated_at":2952,"url":2953,"score":2954},"### Description\n\nIm using a prefix in nuxt.ui.config for nuxtui components\n```\n // nuxt ui settings\n ui: {\n colorMode: false, // disable light dark\n prefix: \"Nuxtui\", // component name prefix\n },\n```\n\nNow when I use the code from the table documentation (https://ui3.nuxt.dev/components/table#columns)\nI am getting a warning that UAvatar (which is linked to UBadge somehow) should be defined as custom Element.\n\n\n\n```\nconst nuxtuiBadge = resolveComponent(\"NuxtuiBadge\");\n\n....\n\ncell: ({ row }) => {\n const color = {\n true: \"success\" as const,\n false: \"error\" as const,\n }[row.getValue(\"isActive\") as string];\n\n return h(\n nuxtuiBadge,\n { class: \"capitalize\", variant: \"subtle\", color },\n () => (row.getValue(\"isActive\") ? \"Aktiv\" : \"Inaktiv\")\n );\n},\n\n....\n```\n\n\nDefining UAvatar as a custom element in nuxt.config solves the warning but isnt it a bug?",[2945,2948,2949],{"name":2946,"color":2947},"duplicate","cfd3d7",{"name":2897,"color":2898},{"name":2869,"color":2870},3218,"UAvatar warning when using nuxtui prefix, UBadge and h in table cell","2025-02-01T11:31:15Z","https://github.com/nuxt/ui/issues/3218",0.7490662,{"description":2956,"labels":2957,"number":2962,"owner":2875,"repository":2876,"state":2913,"title":2963,"updated_at":2964,"url":2965,"score":2966},"### Description\n\nHello, i was wondering if its possible to create something similar to this perhaps using the existing radio-group component.\r\n\r\nExample: https://tailwindui.com/components/application-ui/forms/radio-groups\r\n\u003Cimg width=\"1201\" alt=\"Screenshot 2024-01-11 at 7 59 09 PM\" src=\"https://github.com/nuxt/ui/assets/33962719/5c1bd9cb-7c96-4306-83c5-46eda713de10\">\r\n\n\n### Additional context\n\n_No response_",[2958,2959,2960],{"name":2946,"color":2947},{"name":2866,"color":2867},{"name":2961,"color":2873},"wontfix-v2",1221,"Radio Groups cards","2025-03-24T15:01:33Z","https://github.com/nuxt/ui/issues/1221",0.74954605,{"description":2968,"labels":2969,"number":2974,"owner":2875,"repository":2876,"state":2913,"title":2975,"updated_at":2976,"url":2977,"score":2978},"### Description\n\nI have a Slideover with some checkboxes from a 3rd party library. Whenever I close the slideover all values are lost. \r\n\r\nUsing just headless UI I can solve this by using `:unmount=\"false\"` on the `Dialog` and `TransitionRoot` but can't find anything similar on the slideover.\r\n\r\nDid I miss something here?\r\n\r\n\r\nCheers",[2970,2971],{"name":2897,"color":2898},{"name":2972,"color":2973},"upstream","78bddb",1357,"Slideover loosing state","2025-03-28T17:28:27Z","https://github.com/nuxt/ui/issues/1357",0.7594171,{"description":2980,"labels":2981,"number":2983,"owner":2875,"repository":2876,"state":2913,"title":2984,"updated_at":2985,"url":2986,"score":2987},"Currently, portal components (modals, popovers, etc.) are directly attached to the root of the body. It would be beneficial to allow specifying their destination within the configuration .This would provide greater control over rendering order and potential styling conflicts, especially in complex applications with open shadow Dom. \n\nFor instance, a developer might want to render a modal within a specific container to inherit styles or avoid interference with other elements on the page (I currently using Nuxt ui as a web component withing WordPress). \n\nThe proposed configuration option could be a CSS selector string, allowing for flexible targeting of any existing element in the DOM defaulting to 'body'. ",[2982],{"name":2869,"color":2870},3687,"Allow specify portal destination for all portaled components","2025-04-21T15:42:56Z","https://github.com/nuxt/ui/issues/3687",0.75966895,["Reactive",2989],{},["Set"],["ShallowReactive",2992],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fwO96iWFteKGyxIJYA_OeC336Xuoz-978WrOYQxLue-o":-1},"/nuxt/test-utils/679"]