`\n\nit doesn't work that way\n\nI really ask for help!",[1984,1987],{"name":1985,"color":1986},"question","d876e3",{"name":1988,"color":1989},"v3","49DCB8",3098,"nuxt","ui","open","Table filtered, sorting fetch","2025-01-14T11:05:37Z","https://github.com/nuxt/ui/issues/3098",0.6662819,{"description":1999,"labels":2000,"number":2003,"owner":1991,"repository":1992,"state":1993,"title":2004,"updated_at":2005,"url":2006,"score":2007},"### 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",[2001,2002],{"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.68158984,{"description":2009,"labels":2010,"number":2017,"owner":1991,"repository":1992,"state":1993,"title":2018,"updated_at":2019,"url":2020,"score":2021},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.9.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.8.3\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@2.19.2, nuxt-svgo@4.0.9, @pinia/nuxt@0.9.0, pinia-plugin-persistedstate/nuxt, @nuxtjs/i18n@9.1.0, nuxt-jsonld@2.1.0, @nuxtjs/robots@5.0.0, nuxt-gtag@3.0.2, @sentry/nuxt/module@8.42.0, nuxt-time@1.0.3, @nuxt/eslint@0.7.2\n- Build Modules: -\n\n\n### Version\n\nv2.19.2\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-ncxoznzw\n\n### Description\n\nIf you define your own color for tailwinds, and attempt to use it on a UButton component with the link variant, it will not work and give the following error:\n\n```\n500\nvariant?.replaceAll is not a function\n\nat ComputedRefImpl.fn (https://nuxtui-0mn3--3000--fc837ba8.local-credentialless.webcontainer.io/_nuxt/node_modules/.pnpm/@nuxt+ui@2.19.2_vite@6.0.3_vue@3.5.13/node_modules/@nuxt/ui/dist/runtime/components/elements/Button.js:142:18)\nat refreshComputed (https://nuxtui-0mn3--3000--fc837ba8.local-credentialless.webcontainer.io/_nuxt/node_modules/.pnpm/@vue+reactivity@3.5.13/node_modules/@vue/reactivity/dist/reactivity.esm-bundler.js?v=177a248a:353:29)\nat get value (https://nuxtui-0mn3--3000--fc837ba8.local-credentialless.webcontainer.io/_nuxt/node_modules/.pnpm/@vue+reactivity@3.5.13/node_modules/@vue/reactivity/dist/reactivity.esm-bundler.js?v=177a248a:1558:5)\nat unref (https://nuxtui-0mn3--3000--fc837ba8.local-credentialless.webcontainer.io/_nuxt/node_modules/.pnpm/@vue+reactivity@3.5.13/node_modules/@vue/reactivity/dist/reactivity.esm-bundler.js?v=177a248a:1431:29)\nat Object.get (https://nuxtui-0mn3--3000--fc837ba8.local-credentialless.webcontainer.io/_nuxt/node_modules/.pnpm/@vue+reactivity@3.5.13/node_modules/@vue/reactivity/dist/reactivity.esm-bundler.js?v=177a248a:1437:64)\nat Object.get (https://nuxtui-0mn3--3000--fc837ba8.local-credentialless.webcontainer.io/_nuxt/node_modules/.pnpm/@vue+runtime-core@3.5.13/node_modules/@vue/runtime-core/dist/runtime-core.esm-bundler.js?v=177a248a:3099:26)\nat Proxy._sfc_render (https://nuxtui-0mn3--3000--fc837ba8.local-credentialless.webcontainer.io/_nuxt/node_modules/.pnpm/@nuxt+ui@2.19.2_vite@6.0.3_vue@3.5.13/node_modules/@nuxt/ui/dist/runtime/components/elements/Button.js:199:17)\nat renderComponentRoot (https://nuxtui-0mn3--3000--fc837ba8.local-credentialless.webcontainer.io/_nuxt/node_modules/.pnpm/@vue+runtime-core@3.5.13/node_modules/@vue/runtime-core/dist/runtime-core.esm-bundler.js?v=177a248a:6521:16)\nat hydrateSubTree (https://nuxtui-0mn3--3000--fc837ba8.local-credentialless.webcontainer.io/_nuxt/node_modules/.pnpm/@vue+runtime-core@3.5.13/node_modules/@vue/runtime-core/dist/runtime-core.esm-bundler.js?v=177a248a:5309:32)\nat ReactiveEffect.componentUpdateFn [as fn] (https://nuxtui-0mn3--3000--fc837ba8.local-credentialless.webcontainer.io/_nuxt/node_modules/.pnpm/@vue+runtime-core@3.5.13/node_modules/@vue/runtime-core/dist/runtime-core.esm-bundler.js?v=177a248a:5334:13)\n```\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2011,2014],{"name":2012,"color":2013},"bug","d73a4a",{"name":2015,"color":2016},"triage","ffffff",2860,"[UButton] Using a custom color on the link variant causes an error","2025-02-06T03:16:14Z","https://github.com/nuxt/ui/issues/2860",0.68582445,{"description":2023,"labels":2024,"number":2029,"owner":1991,"repository":1992,"state":1993,"title":2030,"updated_at":2031,"url":2032,"score":2033},"### Description\n\nHi,\ni am working on a project where i am using the Table component with a couple of sortable columns, where i need to access the sorted list from the table. i can see the sorted list in the component, but it isn't exposed and also not included in any event.\n\nis there any way i am not aware of to access the sorted list? ",[2025,2026],{"name":1985,"color":1986},{"name":2027,"color":2028},"stale","ededed",3289,"Table: access sorted list","2025-03-20T02:03:08Z","https://github.com/nuxt/ui/issues/3289",0.7017289,{"description":2035,"labels":2036,"number":2042,"owner":1991,"repository":1992,"state":2043,"title":2044,"updated_at":2045,"url":2046,"score":2047},"### 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_",[2037,2040,2041],{"name":2038,"color":2039},"enhancement","a2eeef",{"name":1988,"color":1989},{"name":2015,"color":2016},3225,"closed","Expose close event for USlideover (Overlay & Button)","2025-03-28T17:34:38Z","https://github.com/nuxt/ui/issues/3225",0.61903816,{"description":2049,"labels":2050,"number":2054,"owner":1991,"repository":1992,"state":2043,"title":2055,"updated_at":2056,"url":2057,"score":2058},"### 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```",[2051,2052,2053],{"name":2012,"color":2013},{"name":1988,"color":1989},{"name":2015,"color":2016},3719,"Toast does not always dispose","2025-04-02T07:18:01Z","https://github.com/nuxt/ui/issues/3719",0.6275459,{"description":2060,"labels":2061,"number":2064,"owner":1991,"repository":1992,"state":2043,"title":2065,"updated_at":2066,"url":2067,"score":2068},"### Description\n\nI was trying to add a bit of margin around the Slideover to look like this:\n\n\n\nI think it can be done cleanly if there was a `\u003Cdiv>` wrapping the whole [DialogContent](https://github.com/nuxt/ui/blob/71728d3c3fa95255db03448c8b87fb75bc2d805c/src/runtime/components/Slideover.vue#L129C7-L129C21)\n\nHow do you suggest to achieve it? \nThank you",[2062,2063],{"name":1985,"color":1986},{"name":1988,"color":1989},3390,"How to add margins around the Slideover panel?","2025-02-25T15:36:40Z","https://github.com/nuxt/ui/issues/3390",0.6554401,{"description":2070,"labels":2071,"number":2080,"owner":1991,"repository":1992,"state":2043,"title":2081,"updated_at":2082,"url":2083,"score":2084},"### 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```",[2072,2073,2076,2077,2078],{"name":2012,"color":2013},{"name":2074,"color":2075},"needs reproduction","CB47CF",{"name":1988,"color":1989},{"name":2015,"color":2016},{"name":2079,"color":2028},"closed-by-bot",3303,"open Popover manually","2025-03-25T02:04:46Z","https://github.com/nuxt/ui/issues/3303",0.66982275,{"description":2086,"labels":2087,"number":2091,"owner":1991,"repository":1992,"state":2043,"title":2092,"updated_at":2093,"url":2094,"score":2095},"### For what version of Nuxt UI are you suggesting this?\n\nv2.x\n\n### Description\n\nMay already be a way to do this but if not It would be nice to specify a variant for light and dark on a component. \nFor instance outline inputs on light mode and soft for dark mode. \n\n` \u003CUInput variant=\"{light: 'outline', dark: 'soft'}\" />\n`\n\n### Additional context\n\n_No response_",[2088,2089],{"name":2038,"color":2039},{"name":2090,"color":2016},"wontfix-v2",2737,"Specify a components variant for each color mode.","2025-03-03T22:31:17Z","https://github.com/nuxt/ui/issues/2737",0.6712103,{"description":2097,"labels":2098,"number":2099,"owner":1991,"repository":2100,"state":2043,"title":2101,"updated_at":2102,"url":2103,"score":2104},"### Environment\n\nDocs issue:\r\nFirefox browser.\n\n### Reproduction\n\nGo on nuxt.com and scroll down to see the footer.\r\nLook at the theme switch. Doable with even OS light and dark modes.\r\n\r\n\r\n\n\n### Describe the bug\n\nTheme switch is not showing the exact mode used by the docs website.\r\nBy default, it shows the light mode as selected where the dark mode is set.\n\n### Additional context\n\nOnly visible on Firefox.\n\n### Logs\n\n_No response_",[],1230,"nuxt.com","Theme switch of docs default value does not sync","2023-10-10T14:45:33Z","https://github.com/nuxt/nuxt.com/issues/1230",0.6762109,["Reactive",2106],{},["Set"],["ShallowReactive",2109],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"63D8oQGfrX4wOyJEB8DtVBzjgDPhEFlZsdEgF1Uy51M":-1},"/nuxt/ui/3305"]