\n```\n\nWould it be relevant to add a global attribute to components like Button, Badge, etc., to force their appearance in dark (or light) mode, regardless of the global setting? This would ensure better visual consistency when these elements are placed on a colored background (e.g., `UPageCTA` with `solid` variant).\n\n### Additional context\n\n_No response_",[3019,3022,3025],{"name":3020,"color":3021},"enhancement","a2eeef",{"name":3023,"color":3024},"v3","49DCB8",{"name":3026,"color":3027},"triage","ffffff",3307,"nuxt","ui","open","Better handling of `UButton`, `UBadge`, … colors on colored backgrounds","2025-02-13T19:05:27Z","https://github.com/nuxt/ui/issues/3307",0.6708888,{"description":3037,"labels":3038,"number":3043,"owner":3029,"repository":3030,"state":3031,"title":3044,"updated_at":3045,"url":3046,"score":3047},"### Description\n\nHi, is there currently a way or planed feature to animate the tr that gets expanded?\nAtm it just pops in and isnt a great ux.\n\nhttps://ui3.nuxt.dev/components/table#with-expandable-rows",[3039,3042],{"name":3040,"color":3041},"question","d876e3",{"name":3023,"color":3024},3305,"UTable tr expand animation","2025-02-13T05:50:31Z","https://github.com/nuxt/ui/issues/3305",0.6829564,{"description":3049,"labels":3050,"number":3052,"owner":3029,"repository":3053,"state":3031,"title":3054,"updated_at":3055,"url":3056,"score":3057},"### Describe the feature\n\nNuxtHub enforce build to cloudflare but test-utils only refer to node build location, so if I use setup() with build: true it will resolve to error, for the workaround now is using host that point to the dev server that can handle NuxtHub related features.\n\n### Additional information\n\n- [ ] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3051],{"name":3020,"color":3021},934,"test-utils","Support non-node build targets for e2e testing","2024-12-05T06:38:10Z","https://github.com/nuxt/test-utils/issues/934",0.72030234,{"description":3059,"labels":3060,"number":3064,"owner":3029,"repository":3030,"state":3065,"title":3066,"updated_at":3067,"url":3068,"score":3069},"### Description\n\nI’ve been using USlideover from NuxtUI (v3), and I noticed that there’s no event triggered when clicking on the overlay (outside of the slideover). This makes it tricky to detect when a user dismisses it by clicking outside, rather than using the close button.\n\nIt would be super helpful if USlideover emitted an event whenever it’s closed—whether that’s via the close button or the overlay. That way, we could easily handle any necessary logic when the slideover is dismissed.\n\nIf exposing a close event isn’t feasible, maybe the overlay could be made accessible as a slot? That way, we could wrap it in our own template and attach a @click event directly. This would give us more flexibility in handling interactions.\n\nI took a look at the source code, and it seems like these interactions are already handled internally, but they aren’t exposed as events:\n🔗 [Slideover.vue](https://github.com/nuxt/ui/blob/v3/src/runtime/components/Slideover.vue)\n\nWould be awesome to see this in a future update.\n\n### Additional context\n\n_No response_",[3061,3062,3063],{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3026,"color":3027},3225,"closed","Expose close event for USlideover (Overlay & Button)","2025-03-28T17:34:38Z","https://github.com/nuxt/ui/issues/3225",0.679874,{"description":3071,"labels":3072,"number":3078,"owner":3029,"repository":3030,"state":3065,"title":3079,"updated_at":3080,"url":3081,"score":3082},"### Environment\n\n- Operating System: Linux\n- Node Version: v20.12.0\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.8\n- Package Manager: npm@10.5.0\n- Builder: -\n- User Config: modules, devtools, compatibilityDate, future\n- Runtime Modules: @nuxt/ui@3.0.2\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/white-butterfly-699yhh\n\n### Description\n\n1. Open the modal via the open button\n2. Open toast(s) via the open button\n3. click modal overlay to dispose it \n4. click any toast (dont click close button)\n5. mouse leave does not count down toasts anymore (click outside does enable countdown again) \n\n---------\nYou can also do this programmatically by closing the modal while adding toasts.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3073,3076,3077],{"name":3074,"color":3075},"bug","d73a4a",{"name":3023,"color":3024},{"name":3026,"color":3027},3719,"Toast does not always dispose","2025-04-02T07:18:01Z","https://github.com/nuxt/ui/issues/3719",0.688656,{"description":3084,"labels":3085,"number":3092,"owner":3029,"repository":3029,"state":3065,"title":3093,"updated_at":3094,"url":3095,"score":3096},"Hi. We have various issues reported for `scrollBehavior` not behaving as desired. Maybe use-cases differ but almost all of them are related to the same known issue and we are aware and plan to help fixing it. Please don't make/reopen duplicated issues as there is enough info about the problem.It just makes the process harder. As of always contributions and PRs are appreciated to both `vue-router` and `nuxt` for possible fixes.\r\n\r\n### vue-router\r\n- Handle scrollBehaviour with transitions (vuejs/vue-router#1263)\r\n- Another detail of scrollBehavior wrapped in transition(vuejs/vue-router#1373)\r\n- scrollBehavior doesn't work for initial route in Firefox (vuejs/vue-router#1585)\r\n- Need a way to set what scroll position is saved (vuejs/vue-router#1187)\r\n- Navigating back should retain the scroll position. (vuejs/vue-router#1669)\r\n- Support parent container for scroll behavior (vuejs/vue-router#1249)\r\n- Calcurated scroll position is incorrect in some browser with animation (vuejs/vue-router#1530)\r\n\r\n\r\n### Issues\r\n- Strange behavior in Firefox browser when page transition (#1373)\r\n- What causes a glitch when page transition in Firefox? (#1002)\r\n- Delayed scroll top possible? (#1355)\r\n- ScrollBehavior: Fires too early (#1036)\r\n- Navigating back should retain the scroll position. (#1182)\r\n\r\n### Reproductions\r\n\r\n- https://github.com/krestaino/scroll-position-nuxt (@krestaino, #1182)\r\n- http://jsfiddle.net/qw4hbgek (@posva, vuejs/vue-router#1263)\r\n- http://jsfiddle.net/xctnu8r3/2 (@nickforddesign , vuejs/vue-router#1373)\r\n- https://github.com/vuejs/vue-router/tree/dev/examples/scroll-behavior (@hworld, vuejs/vue-router#1585)\r\n- http://codepen.io/brad426/pen/pezRge (@brad426)\r\n\r\n\r\n### Misc\r\n- https://nuxtjs.org/faq/css-flash\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1219\">#c1219\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3086,3089],{"name":3087,"color":3088},"available soon","6de8b0",{"name":3090,"color":3091},"2.x","d4c5f9",1376,"scrollBehavior Glitches","2023-01-18T15:41:42Z","https://github.com/nuxt/nuxt/issues/1376",0.7025569,{"description":3098,"labels":3099,"number":3102,"owner":3029,"repository":3103,"state":3065,"title":3104,"updated_at":3105,"url":3106,"score":3107},"- [ ] Integrations\n- [ ] Resources\n- [ ] ...",[3100],{"name":3074,"color":3101},"ff281a",394,"nuxt.com","[Navbar] Mobile navigation on refresh for links outside of `content/`","2022-05-20T17:04:16Z","https://github.com/nuxt/nuxt.com/issues/394",0.7028659,{"description":3109,"labels":3110,"number":3102,"owner":3029,"repository":3053,"state":3065,"title":3111,"updated_at":3112,"url":3113,"score":3107},"I am checking the official documentation of Nuxt and it says that this project is still in development. \r\n\r\n\r\n\r\n- [Nuxt/Testing ](https://nuxt.com/docs/getting-started/testing)\r\n\r\nSo, My question is if this data is correct because I don't see any warning from your side. ",[],"Could I use @nuxt/test-utils for testing production apps?","2023-12-02T00:13:09Z","https://github.com/nuxt/test-utils/issues/394",{"description":3115,"labels":3116,"number":3118,"owner":3029,"repository":3030,"state":3065,"title":3119,"updated_at":3120,"url":3121,"score":3122},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v20.14.0\r\n- Nuxt Version: 3.12.4\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: pnpm@9.7.1\r\n- Builder: -\r\n- User Config: runtimeConfig, extends, modules, ui, colorMode, routeRules, devtools, typescript, future, eslint, nitro, i18n, compatibilityDate\r\n- Runtime Modules: @nuxt/eslint@0.5.0, @nuxt/fonts@0.7.1, @nuxt/ui@2.18.4, @vueuse/nuxt@10.11.0, @nuxtjs/i18n@8.5.0\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Version\r\n\r\nPro 1.4.1\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-ui-u6tm1b?file=app.vue\r\n\r\n### Description\r\n\r\nWhen using a `v-model` prop with some initial object values (such as fetched already selected data from backend), the `\u003CUSelectMenu>` component doesn't show these as selected and seems to ignore them completely.\r\n\r\nEven when selecting the same objects again, it just seems to add them to the array and disregard anything, that was there previously.\r\n\r\n### Additional context\r\n\r\nThe behaviour changes when setting the `by` prop. In my case, I set it to `id`, after which I can see the object as selected, **but only** in the dropdown.\r\nThis also allows me to edit the data as normal. (Select/Deselect)\r\nHowever the button itself still shows `0 selected`.\r\n\r\n### Logs\r\n\r\n_No response_",[3117],{"name":3074,"color":3075},2086,"SelectMenu ignoring initial object values","2024-11-12T17:12:26Z","https://github.com/nuxt/ui/issues/2086",0.7030349,{"description":3124,"labels":3125,"number":3128,"owner":3029,"repository":3030,"state":3065,"title":3129,"updated_at":3130,"url":3131,"score":3132},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.11.1\n- Nuxt Version: 3.13.2\n- CLI Version: 3.14.0\n- Nitro Version: 2.9.7\n- Package Manager: bun@1.1.33\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Version\n\nv3.0.0-alpha.7\n\n### Reproduction\n\n```ts\nexport default defineAppConfig({\n ui: {\n colors: {\n neutral: \"zinc\",\n primary: \"rose\",\n },\n button: {\n compoundVariants: [\n {\n color: \"neutral\",\n variant: \"outline\",\n class:\n \"ring ring-inset ring-[var(--ui-border-accented)] text-[var(--ui-text)] bg-[var(--ui-bg)] hover:bg-[var(--ui-bg-elevated)] disabled:bg-[var(--ui-bg)] aria-disabled:bg-[var(--ui-bg)] focus-visible:ring-2 focus-visible:ring-[var(--ui-border-inverted)]\",\n },\n ],\n },\n },\n});\n```\n\n```\nType '{ color: \"neutral\"; variant: \"outline\"; class: string; }[]' is not assignable to type 'DeepPartial\u003C({ color: \"primary\"; variant: \"solid\"; class: string; size?: undefined; square?: undefined; loading?: undefined; leading?: undefined; trailing?: undefined; } | { color: \"secondary\"; variant: \"solid\"; ... 5 more ...; trailing?: undefined; } | ... 46 more ... | { ...; })[], string>'.\n Type '{ color: \"neutral\"; variant: \"outline\"; class: string; }[]' is not assignable to type '{ [key: string]: string | TightMap\u003Cstring>; }'.\n Index signature for type 'string' is missing in type '{ color: \"neutral\"; variant: \"outline\"; class: string; }[]'.ts(2322)\n```\n\n### Description\n\nHi :) I am getting type errors when using `compoundVariant`. \n\nFor example, here is my `app.config.ts`:\n\n```ts\nexport default defineAppConfig({\n ui: {\n colors: {\n neutral: \"zinc\",\n primary: \"rose\",\n },\n button: {\n compoundVariants: [\n {\n color: \"neutral\",\n variant: \"outline\",\n class:\n \"ring ring-inset ring-[var(--ui-border-accented)] text-[var(--ui-text)] bg-[var(--ui-bg)] hover:bg-[var(--ui-bg-elevated)] disabled:bg-[var(--ui-bg)] aria-disabled:bg-[var(--ui-bg)] focus-visible:ring-2 focus-visible:ring-[var(--ui-border-inverted)]\",\n },\n ],\n },\n },\n});\n```\n\nI am getting the following type error for `compoundVariants`:\n```\nType '{ color: \"neutral\"; variant: \"outline\"; class: string; }[]' is not assignable to type 'DeepPartial\u003C({ color: \"primary\"; variant: \"solid\"; class: string; size?: undefined; square?: undefined; loading?: undefined; leading?: undefined; trailing?: undefined; } | { color: \"secondary\"; variant: \"solid\"; ... 5 more ...; trailing?: undefined; } | ... 46 more ... | { ...; })[], string>'.\n Type '{ color: \"neutral\"; variant: \"outline\"; class: string; }[]' is not assignable to type '{ [key: string]: string | TightMap\u003Cstring>; }'.\n Index signature for type 'string' is missing in type '{ color: \"neutral\"; variant: \"outline\"; class: string; }[]'.ts(2322)\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3126,3127],{"name":3074,"color":3075},{"name":3023,"color":3024},2481,"Type error on `compoundVariants`","2024-10-28T21:43:49Z","https://github.com/nuxt/ui/issues/2481",0.70335245,["Reactive",3134],{},["Set"],["ShallowReactive",3137],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$ft30Goar1YD9Or-f9oOX0jAIOmUZXQnOip2DJWf6Jp_Q":-1},"/nuxt/nuxt.com/1230"]