\n```\n\nAfter:\n```html\n\u003C!-- `ui` prop is the same as `app.config.ts` theming config\n\u003CUTheme :ui=\"{\n formField: {\n\t slots: {\n\t root: \"flex max-sm:flex-col justify-between items-center gap-4\",\n\t},\n },\n}\">\n \u003CUForm ...>\n \u003CUFormField ...>\n ...\n \u003CUFormField>\n \u003CUFormField ...>\n ...\n \u003CUFormField>\n \u003CUForm/>\n\u003C/UTheme>\n```\n\n## Benefits\n- Easily componentized. I could create a `AppForm` component which contains the `UTheme` usage with a slot, so now its 1 line to get the exact theming that I want. This makes consistency across the app really easy.\n- Nestable - If implemented with provide/inject, you could have an infinite number of UTheme's nested and it would take the latest one\n\n## Implementation\nI'd tentatively be willing to implement this. My approach would be:\n- Create `UTheme`, it should have a `ui` and `uiPro` prop, each of which take the same type as the `app.config.ts`\n- `provide()` those props\n- `inject()` those props into each component and merge with passed in `ui` field.\n- Theme priority order should be:\n 1. `ui` prop passed to component\n 2. `ui` prop coming from UTheme component\n 3. `ui` config coming from `app.config.ts`\n\n### Additional context\n\n_No response_",[3050,3051,3052],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3025,"color":3026},4250,"UTheme component","2025-05-28T22:24:36Z","https://github.com/nuxt/ui/issues/4250",0.75549704,{"description":3059,"labels":3060,"number":3064,"owner":3028,"repository":3029,"state":3030,"title":3065,"updated_at":3066,"url":3067,"score":3068},"### Description\n\nHello 👋,\n\nI'm building a dashboard and I often need to put a table in a modal. Currently, I have to manually change the style of the modal and the table to match perfectly.\n\nSee this example: https://stackblitz.com/edit/github-2aatsynx?file=app%2Fpages%2Findex.vue\n\nTo solve this, I have to solution in mind:\n\n1. props to change the table and modal class;\n2. injection key to tell the table that it is in a modal.\n\nTo be honest, I don't like the second one as it removes a lot of flexibility.\n\nThe first one will introduce some new variants to all customization globally which is better than the current manual customization. For a Modal component, a new `table` (or `body-padding` or something even more generic but used to remove the padding from the body) props and a `modal` props for the table to align the internal padding.\n\nMaybe there is more solutions to this!\n\n### Additional context\n\n_No response_",[3061,3062,3063],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3025,"color":3026},4366,"Simplify table usage in modals","2025-06-17T07:42:04Z","https://github.com/nuxt/ui/issues/4366",0.76937294,{"description":3070,"labels":3071,"number":3075,"owner":3028,"repository":3029,"state":3076,"title":3077,"updated_at":3078,"url":3079,"score":3080},"### Description\n\nThe new CheckboxGroup component lacks the `table` variant found on the RadioGroup component. Since these components will often appear together in forms, it would be preferable to have the table variant for both of them.\n\nThis is already easily achieved with the new component by adding the RadioGroup styles to the `item` ui prop. I think it should be possible to make this change just by adding the styles to checkbox-group.ts. I'm happy to make a pull request and make the changes.\n\n### Additional context\n\n_No response_",[3072,3073,3074],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3025,"color":3026},3994,"closed","[CheckboxGroup] Add `variant=\"table\"` to match RadioGroup variants","2025-05-13T12:28:16Z","https://github.com/nuxt/ui/issues/3994",0.6110914,{"description":3082,"labels":3083,"number":3093,"owner":3028,"repository":3029,"state":3076,"title":3094,"updated_at":3095,"url":3096,"score":3097},"### Description\n\nI would like for the RadioGroup on table mode to be overflowed and create a square of options instead of being rigid and forcing scrolling\n\nAs seen on \"date\" below\n\n\n\n### Additional context\n\n_No response_",[3084,3085,3088,3089,3090],{"name":3019,"color":3020},{"name":3086,"color":3087},"needs reproduction","CB47CF",{"name":3022,"color":3023},{"name":3025,"color":3026},{"name":3091,"color":3092},"closed-by-bot","ededed",4091,"[RadioGroup] Allow wrapping","2025-05-14T02:09:23Z","https://github.com/nuxt/ui/issues/4091",0.70158494,{"description":3099,"labels":3100,"number":3106,"owner":3028,"repository":3029,"state":3076,"title":3107,"updated_at":3108,"url":3109,"score":3110},"### Description\n\nA toggle button would be very useful. The closest thing we have is radio group or checkbox group. \nInspired by:\n[VBtnToggle](https://vuetifyjs.com/en/components/button-groups/)\n[VChipGroup](https://vuetifyjs.com/en/components/chip-groups/#usage)\n\nSimilar functionality could be achieved on RadioGroup by making unchecking possible (so null values are selectable)\nAND/OR\nBy adding a v-model to the button component, and model-active variants (so you can change the color, varient, icon, etc when checked). The model would be either a Boolean or an array of values similar to Vuetify.\n\n### Additional context\n\n_No response_",[3101,3104,3105],{"name":3102,"color":3103},"duplicate","cfd3d7",{"name":3019,"color":3020},{"name":3022,"color":3023},4246,"[Button] Toggle / V-Model","2025-05-28T17:19:55Z","https://github.com/nuxt/ui/issues/4246",0.7223517,{"description":3112,"labels":3113,"number":3117,"owner":3028,"repository":3029,"state":3076,"title":3118,"updated_at":3119,"url":3120,"score":3121},"### Description\n\nI want to allow multiple values selection in radio group, but cannot find any prop of way from the documentation\n\n### Additional context\n\n_No response_",[3114,3115,3116],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3025,"color":3026},4143,"Multiple Value selection in radio group","2025-05-13T13:57:53Z","https://github.com/nuxt/ui/issues/4143",0.7416192,{"description":3123,"labels":3124,"number":3128,"owner":3028,"repository":3029,"state":3076,"title":3129,"updated_at":3130,"url":3131,"score":3132},"### Description\n\nThis is a re-opening of #1484 but for v3. It seems in the transition from v2 to v3, giving the indicators (now \"dots\") ARIA \"tab\" roles was lost. While I did mention it in my original issue, I don't believe my original PR accounted for when multiple items would be displayed at the same time. Perhaps the changes for v3 can take that into account.\n\n### Additional context\n\n_No response_",[3125,3126,3127],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3025,"color":3026},4494,"Carousel component could be made more accessible (v3).","2025-07-10T12:18:41Z","https://github.com/nuxt/ui/issues/4494",0.75219095,{"description":3134,"labels":3135,"number":3139,"owner":3028,"repository":3029,"state":3076,"title":3140,"updated_at":3141,"url":3142,"score":3143},"### Description\n\nWhen a dot is selected in the UCarousel component, we get no attribute in the element : \n\n- no data-selected\n- no aria-current for accessibility\n\nSince there is no dots/dot slot, we have no possibility to style these dots when selected or not. The only difference is the bg style being either bg-accented or bg-inverted, which is overwritten if we actually style the background.\n\nIs there any way to add these attributes ? At least for accessibility.\n\n### Additional context\n\n_No response_",[3136,3137,3138],{"name":3019,"color":3020},{"name":3022,"color":3023},{"name":3025,"color":3026},4403,"UCarousel selected dot has no attribute","2025-07-07T10:09:58Z","https://github.com/nuxt/ui/issues/4403",0.7611457,["Reactive",3145],{},["Set"],["ShallowReactive",3148],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$flDP3Lrdl75k4V0iC3ItOhlGzcsAwsu-kMf4qUOY9Whg":-1},"/nuxt/ui/4545"]