\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_",[2001,2004,2005],{"name":2002,"color":2003},"enhancement","a2eeef",{"name":1988,"color":1989},{"name":2006,"color":2007},"triage","ffffff",3307,"Better handling of `UButton`, `UBadge`, … colors on colored backgrounds","2025-02-13T19:05:27Z","https://github.com/nuxt/ui/issues/3307",0.68322074,{"description":2014,"labels":2015,"number":2018,"owner":1991,"repository":1992,"state":1993,"title":2019,"updated_at":2020,"url":2021,"score":2022},"### Description\n\nCurrently, when I use `UAvatar` and the user's photo returns a 404, it generates an `\u003Cimg>` with the broken image icon:\n\n\nIs there a way to make the image that returns 404 display text from the alt instead?\nIn the documentation it says:\n>When no icon or text is provided, the initials of the `alt` prop are used as fallback\n\nCan `alt` also be used as a fallback when the image is broken?\n\n\n\nExample:\n\n",[2016,2017],{"name":1985,"color":1986},{"name":1988,"color":1989},3809,"[UAvatar] If the image does not exist, return text","2025-04-06T16:07:33Z","https://github.com/nuxt/ui/issues/3809",0.69408363,{"description":2024,"labels":2025,"number":2027,"owner":1991,"repository":2028,"state":1993,"title":2029,"updated_at":2030,"url":2031,"score":2032},"### 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).",[2026],{"name":2002,"color":2003},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.7107918,{"description":2034,"labels":2035,"number":2039,"owner":1991,"repository":1992,"state":2040,"title":2041,"updated_at":2042,"url":2043,"score":2044},"### 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_",[2036,2037,2038],{"name":2002,"color":2003},{"name":1988,"color":1989},{"name":2006,"color":2007},3225,"closed","Expose close event for USlideover (Overlay & Button)","2025-03-28T17:34:38Z","https://github.com/nuxt/ui/issues/3225",0.693719,{"description":2046,"labels":2047,"number":2053,"owner":1991,"repository":1992,"state":2040,"title":2054,"updated_at":2055,"url":2056,"score":2057},"### 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```",[2048,2051,2052],{"name":2049,"color":2050},"bug","d73a4a",{"name":1988,"color":1989},{"name":2006,"color":2007},3719,"Toast does not always dispose","2025-04-02T07:18:01Z","https://github.com/nuxt/ui/issues/3719",0.6966193,{"description":2059,"labels":2060,"number":2070,"owner":1991,"repository":1992,"state":2040,"title":2071,"updated_at":2072,"url":2073,"score":2074},"### Environment\n\nOperating System: Windows 11\nNode Version: v22.14.0\nNuxt Version: 3.15.4\nCLI Version: 3.13.2\nNitro Version: 2.10.4\nPackage Manager: npm@11.1.0\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.12\n\n### Reproduction\n\n.\n\n### Description\n\nI want the Popover component to open when a fetch call is made and the results are displayed in the Popover. For example, I want the search results to be displayed, but as soon as I click on the input, the Popover will be displayed.\n\nThis is my code:\n```\n\u003CUPopover v-model:open=\"search.open\" arrow>\n \u003Cdiv class=\"header-search relative flex flex-row items-center w-full max-w-96\">\n \u003Cinput v-model=\"search.param\"\n class=\"input bg-transparent border rounded-3xl focus:ring-0 outline-0 py-1 px-2 w-full\" />\n \u003C/div>\n \u003Ctemplate #content>\n ...\n \u003C/template>\n \u003C/UPopover>\n```\n\nDid I do something wrong?\nPlease help me.\nThanks\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2061,2062,2065,2066,2067],{"name":2049,"color":2050},{"name":2063,"color":2064},"needs reproduction","CB47CF",{"name":1988,"color":1989},{"name":2006,"color":2007},{"name":2068,"color":2069},"closed-by-bot","ededed",3303,"open Popover manually","2025-03-25T02:04:46Z","https://github.com/nuxt/ui/issues/3303",0.69734365,{"description":2076,"labels":2077,"number":2079,"owner":1991,"repository":1992,"state":2040,"title":2080,"updated_at":2081,"url":2082,"score":2083},"### 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_",[2078],{"name":2049,"color":2050},2086,"SelectMenu ignoring initial object values","2024-11-12T17:12:26Z","https://github.com/nuxt/ui/issues/2086",0.7012149,{"description":2085,"labels":2086,"number":2089,"owner":1991,"repository":2090,"state":2040,"title":2091,"updated_at":2092,"url":2093,"score":2094},"- [ ] Integrations\n- [ ] Resources\n- [ ] ...",[2087],{"name":2049,"color":2088},"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.70287496,{"description":2096,"labels":2097,"number":2089,"owner":1991,"repository":2028,"state":2040,"title":2098,"updated_at":2099,"url":2100,"score":2094},"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",["Reactive",2102],{},["Set"],["ShallowReactive",2105],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"t30Goar1YD9Or-f9oOX0jAIOmUZXQnOip2DJWf6Jp_Q":-1},"/nuxt/nuxt.com/1230"]