` for the rest of the content, which could be either 1 or more DashboardPanels.\n\nThanks in advance!",[2899,2902,2903],{"name":2900,"color":2901},"question","d876e3",{"name":2869,"color":2870},{"name":2904,"color":2905},"pro","5BD3CB",3627,"How to add a persistent Navbar on top of all DashboardPanels inside of a DashboardGroup?","2025-03-19T20:53:14Z","https://github.com/nuxt/ui/issues/3627",0.7003577,{"description":2912,"labels":2913,"number":2915,"owner":2875,"repository":2876,"state":2891,"title":2916,"updated_at":2917,"url":2918,"score":2919},"### Description\n\nCurrent `UTable` can only support multiple selection.\r\nIn my scenario, I want to make it to support both single or multiple selection.\n\n### Additional context\n\n_No response_",[2914],{"name":2866,"color":2867},2065,"UTable can support single selection","2024-09-06T10:17:08Z","https://github.com/nuxt/ui/issues/2065",0.7107503,{"description":2921,"labels":2922,"number":2925,"owner":2875,"repository":2876,"state":2891,"title":2926,"updated_at":2927,"url":2928,"score":2929},"### Description\n\nWould like to modify the default dark mode appearance of the UInput component.\n\nThe first name field is unstyled. The last name field shows my attempt to add styles, but to no effect. \n\nThe v2 component apparently had a `inputClass` that allowed the text and background color to be styled. \n\nIs there a v3 equivalent?\n\nThanks\n\nPS. the password fields are both also unstyled -- they just seem to have a different behaviors dependent on whether any text has been entered.\n\n```\n\u003Ctemplate>\n \u003CUContainer class=\"z-10 max-w-md py-10\">\n \u003CUCard class=\"bg-slate-200 shadow-md dark:bg-slate-600\">\n\n \u003Ctemplate #header>\n \u003Cspan class=\"text-center text-xl font-semibold text-gray-900 dark:text-white\">Sign up\u003C/span>\n \u003C/template>\n\n \u003CUForm\n :state=\"formState\"\n :schema=\"signUpSchema\"\n class=\"space-y-4\"\n @submit=\"onSubmit\">\n \u003Cdiv class=\"flex\">\n \u003CUFormField\n label=\"First Name\"\n name=\"firstName\"\n class=\"mr-3 flex-4\">\n \u003CUInput\n v-model=\"formState.firstName\"\n type=\"text\"\n placeholder=\"First Name\"\n icon=\"i-heroicons-user-solid\"/>\n \u003C/UFormField>\n \u003CUFormField\n label=\"Last Name\"\n name=\"lastName\"\n class=\"flex-5\">\n \u003CUInput\n v-model=\"formState.lastName\"\n type=\"text\"\n placeholder=\"Last Name\"\n icon=\"i-heroicons-user-solid\"\n class=\"text-gray-900 dark:text-white\" /> \u003C!-- has no effect -->\n \u003C/UFormField>\n \u003C/div>\n ...\n```\n\n",[2923,2924],{"name":2900,"color":2901},{"name":2869,"color":2870},3136,"Q: how to style the text and background color of the UInput component?","2025-01-18T00:58:37Z","https://github.com/nuxt/ui/issues/3136",0.7267441,{"description":2931,"labels":2932,"number":2935,"owner":2875,"repository":2876,"state":2891,"title":2936,"updated_at":2937,"url":2938,"score":2939},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.x\n\n### Description\n\nI find that creating an input password with toggle button to show the text felt so verbose. How about adding a default toggle button when the input has password type since it was a good practice for accessibility?\n\n\n\n### Additional context\n\n```html\n\u003C!-- this is easier and shorter to write -->\n\u003CUInput type=\"password\" />\n\n\u003C!-- if we want to hide, we can let slot do the work, or maybe consider adding a properties to hide it. It's more shorter -->\n\u003CUInput type=\"password\">\n \u003Ctemplate #trailing>\u003C/template>\n\u003C/UInput>\n\n\u003C!-- compared to what we must do now as the documentation say -->\n\u003Ctemplate>\n \u003CUInput\n v-model=\"password\"\n placeholder=\"Password\"\n :type=\"show ? 'text' : 'password'\"\n :ui=\"{ trailing: 'pe-1' }\"\n >\n \u003Ctemplate #trailing>\n \u003CUButton\n color=\"neutral\"\n variant=\"link\"\n size=\"sm\"\n :icon=\"show ? 'i-lucide-eye-off' : 'i-lucide-eye'\"\n aria-label=\"show ? 'Hide password' : 'Show password'\"\n :aria-pressed=\"show\"\n aria-controls=\"password\"\n @click=\"show = !show\"\n />\n \u003C/template>\n \u003C/UInput>\n\u003C/template>\n\n\u003Cscript setup lang=\"ts\">\nconst show = ref(false)\nconst password = ref('password')\n\u003C/script>\n```",[2933,2934],{"name":2866,"color":2867},{"name":2869,"color":2870},2806,"input: add toggle password button automatically for type password","2024-12-02T17:21:42Z","https://github.com/nuxt/ui/issues/2806",0.7300922,{"description":2941,"labels":2942,"number":2945,"owner":2875,"repository":2876,"state":2891,"title":2946,"updated_at":2947,"url":2948,"score":2949},"### Description\n\nIn the current implementation the color schemes for primary and success, as well as secondary and info, are overlapping. This creates ambiguity and limits customization options for users who wish to differentiate these colors for better visual distinction.\n\nPrimary and Success : Both use the same green color palette.\nSecondary and Info : Both use the same blue color palette.\nThis overlap forces developers to manually override the CSS variables in the root to achieve distinct colors for each category. For example:\n\n```\n:root {\n--ui-color-primary-50: #ccf1ef;\n--ui-color-primary-100: #99e3df;\n--ui-color-primary-200: #66d5ce;\n--ui-color-primary-300: #33c7be;\n--ui-color-primary-400: #00b9ae;\n--ui-color-primary-500: #00948b;\n--ui-color-primary-600: #006f68;\n--ui-color-primary-700: #004a46;\n--ui-color-primary-800: #002523;\n--ui-color-primary-900: #001311;\n--ui-color-primary-950: #000a08;\n\n--ui-color-secondary-50: #fff6ca;\n--ui-color-secondary-100: #fff3b6;\n--ui-color-secondary-200: #ffefa1;\n--ui-color-secondary-300: #ffec8d;\n--ui-color-secondary-400: #fee564;\n--ui-color-secondary-500: #fedf3c;\n--ui-color-secondary-600: #fed813;\n--ui-color-secondary-700: #e2be01;\n--ui-color-secondary-800: #b49701;\n--ui-color-secondary-900: #9e8401;\n--ui-color-secondary-950: #7a6e01;\n}\n```\n\nDoes it a correct way?",[2943,2944],{"name":2900,"color":2901},{"name":2869,"color":2870},3286,"Request for Distinct Color Schemes for Primary/Success and Secondary/Info","2025-02-11T04:33:39Z","https://github.com/nuxt/ui/issues/3286",0.7328736,{"description":2951,"labels":2952,"number":2956,"owner":2875,"repository":2876,"state":2891,"title":2957,"updated_at":2958,"url":2959,"score":2960},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.12.0\n- Nuxt Version: 3.16.0\n- CLI Version: 3.22.5\n- Nitro Version: 2.11.6\n- Package Manager: pnpm@10.6.2\n- Builder: -\n- User Config: modules, css, runtimeConfig, uiPro, compatibilityDate, devtools, future, experimental\n- Runtime Modules: @nuxt/eslint@1.2.0, @nuxt/ui-pro@3.0.0, @nuxt/content@3.3.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0\n\n### Reproduction\n\n```html\n\u003CProsePre lang=\"yaml\">{{ yaml }}\u003C/ProsePre>\n```\n\n\n### Description\n\nMade sure I have content installed and loaded - renders just fine, copy button shows the ✅ - but nothing is copied\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2953,2954,2955],{"name":2886,"color":2887},{"name":2869,"color":2870},{"name":2872,"color":2873},3545,"Clipboard button doesnt copy content when using ProsePre directly","2025-03-13T00:31:04Z","https://github.com/nuxt/ui/issues/3545",0.73519903,{"description":2962,"labels":2963,"number":2966,"owner":2875,"repository":2876,"state":2891,"title":2967,"updated_at":2968,"url":2969,"score":2970},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v22.7.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.22.2\n- Nitro Version: 2.10.4\n- Package Manager: yarn@1.22.22\n- Builder: -\n- User Config: ssr, imports, devtools, experimental, future, compatibilityDate, alias, runtimeConfig, devServer, typescript, app, css, modules, build, hooks, dayjs, ui\n- Runtime Modules: @nuxt/eslint@1.1.0, @vueuse/nuxt@12.7.0, @nuxt/test-utils/module@3.17.0, dayjs-nuxt@2.1.11, nuxt-svgo@4.0.14, @nuxt/ui@3.0.0-alpha.13, @pinia/nuxt@0.10.1, @pinia/colada-nuxt@0.0.5\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n@nuxt/ui@3.0.0-alpha.13\n\n### Reproduction\n\nno actions, no styles, no nothing\n\n### Description\n\nno actions, no styles, no nothing\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2964,2965],{"name":2886,"color":2887},{"name":2869,"color":2870},3386,"Nothing works","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/3386",0.7408722,{"description":2972,"labels":2973,"number":2983,"owner":2875,"repository":2876,"state":2891,"title":2984,"updated_at":2985,"url":2986,"score":2987},"### Environment\n\nNode 22\nNuxt 4\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0 alpha 10\n\n### Reproduction\n\n1. create a modal and a slideover using useModal and useSlideover\n2. create a button **(first button**) that opens the modal with useModal()\n3. create one as well **(second button**) INSIDE! the slideover that opens the same modal with useModal()\n\n### Description\n\nNow open the modal outside the slideover with the **first button**. Thats set an index I suppose.\nBut now if you open the slideover and click the **second button** which opens the same modal, it appears behind the slideover.\n\nBut if you reload the page, open the slideover first and then press the second button without ever pressing the first button to open the modal it appears infront.\n\n### Additional context\n\n\n\n\n\n### Logs\n\n```shell-script\n\n```",[2974,2975,2978,2979,2980],{"name":2886,"color":2887},{"name":2976,"color":2977},"needs reproduction","CB47CF",{"name":2869,"color":2870},{"name":2872,"color":2873},{"name":2981,"color":2982},"closed-by-bot","ededed",3079,"Modal and slideover z-index bug","2025-03-25T02:04:49Z","https://github.com/nuxt/ui/issues/3079",0.7452149,["Reactive",2989],{},["Set"],["ShallowReactive",2992],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f3vVRT7QKyfny4RZEJl5ydgZB0A0fhof3gqW-kxJCaXY":-1},"/nuxt/ui/2915"]