`\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.6836799,{"description":1999,"labels":2000,"number":2008,"owner":1991,"repository":1992,"state":1993,"title":2009,"updated_at":2010,"url":2011,"score":2012},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.13.1\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.8\n- Package Manager: yarn@4.8.1\n- Builder: -\n- User Config: compatibilityDate, imports, components, devtools, modules, css, fonts, ui\n- Runtime Modules: @nuxt/eslint@1.2.0, @nuxt/fonts@0.11.0, @nuxt/image@1.10.0, @nuxt/test-utils@3.17.2, @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://github.com/nuxt/ui/blob/v3/src/theme/button.ts\n\n### Description\n\nI want to customize a button variant by `size`, `trailing` and `square` params. It works, but the types are broken.\n\nThe line in the `compoundVariants`:\n`{ size: 'md', trailing: true, square: false, class: { trailingIcon: '-mr-1' } }`\n\nErrors:\n`Type '{ trailingIcon: string; }' is not assignable to type 'string'`\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2001,2004,2005],{"name":2002,"color":2003},"bug","d73a4a",{"name":1988,"color":1989},{"name":2006,"color":2007},"triage","ffffff",3738,"Incorrect compound button variants types","2025-03-30T14:32:49Z","https://github.com/nuxt/ui/issues/3738",0.7019438,{"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.7178992,{"description":2024,"labels":2025,"number":2028,"owner":1991,"repository":1992,"state":1993,"title":2029,"updated_at":2030,"url":2031,"score":2032},"### 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",[2026,2027],{"name":1985,"color":1986},{"name":1988,"color":1989},3305,"UTable tr expand animation","2025-02-13T05:50:31Z","https://github.com/nuxt/ui/issues/3305",0.7212043,{"description":2034,"labels":2035,"number":2038,"owner":1991,"repository":1992,"state":2039,"title":2040,"updated_at":2041,"url":2042,"score":2043},"### Description\n\nStyles with tailwindcss 4.0.13 seem to be broken after updating from NuxtUI pervious alpha.\n\n```\n\"dependencies\": {\n \"@iconify-json/ri\": \"1.2.5\",\n \"@nuxt/ui\": \"3.0.0\",\n \"@vueuse/core\": \"12.7.0\",\n \"@vueuse/nuxt\": \"12.7.0\",\n }\n```\nmain.css\n```\n@import 'tailwindcss' theme(static);\n@import '@nuxt/ui';\n```\nHas anyone else ran into this issue and if so how did you fix it?",[2036,2037],{"name":1985,"color":1986},{"name":1988,"color":1989},3525,"closed","Styles issue have upgrade from 3.0.0-alpha.13 to 3.0.0","2025-03-12T23:28:54Z","https://github.com/nuxt/ui/issues/3525",0.6744506,{"description":2045,"labels":2046,"number":2056,"owner":1991,"repository":1992,"state":2039,"title":2057,"updated_at":2058,"url":2059,"score":2060},"### 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```",[2047,2048,2051,2052,2053],{"name":2002,"color":2003},{"name":2049,"color":2050},"needs reproduction","CB47CF",{"name":1988,"color":1989},{"name":2006,"color":2007},{"name":2054,"color":2055},"closed-by-bot","ededed",3303,"open Popover manually","2025-03-25T02:04:46Z","https://github.com/nuxt/ui/issues/3303",0.6843505,{"description":2062,"labels":2063,"number":2065,"owner":1991,"repository":1992,"state":2039,"title":2066,"updated_at":2067,"url":2068,"score":2069},"### 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_",[2064],{"name":2002,"color":2003},2086,"SelectMenu ignoring initial object values","2024-11-12T17:12:26Z","https://github.com/nuxt/ui/issues/2086",0.6873193,{"description":2071,"labels":2072,"number":2076,"owner":1991,"repository":1992,"state":2039,"title":2077,"updated_at":2078,"url":2079,"score":2080},"### 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```",[2073,2074,2075],{"name":2002,"color":2003},{"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.69136465,{"description":2082,"labels":2083,"number":2090,"owner":1991,"repository":1991,"state":2039,"title":2091,"updated_at":2092,"url":2093,"score":2094},"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>",[2084,2087],{"name":2085,"color":2086},"available soon","6de8b0",{"name":2088,"color":2089},"2.x","d4c5f9",1376,"scrollBehavior Glitches","2023-01-18T15:41:42Z","https://github.com/nuxt/nuxt/issues/1376",0.69136554,{"description":2096,"labels":2097,"number":2100,"owner":1991,"repository":1992,"state":2039,"title":2101,"updated_at":2102,"url":2103,"score":2104},"### Description\n\nHi,\n\nhere in the first form in nuxtui2\nhttps://ui.nuxt.com/components/form \nthe behaviour is that the input field is validated after the blur. If there is an error and I correct it, the error is fixed immediately.\n\nIn v3 the behaviour is different. I have seen the prop validateOn so I can change it to blur, but not like first onBlur and then onInput like in v2.\n\nbest,\ngregor",[2098,2099],{"name":2002,"color":2003},{"name":1988,"color":1989},3006,"How can I get the same form validation behaviour as in v2?","2025-01-06T17:48:11Z","https://github.com/nuxt/ui/issues/3006",0.70304537,["Reactive",2106],{},["Set"],["ShallowReactive",2109],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"_NX-4Eg4scSHpUEOJkl_GXsWHBPA4Q5MLZFt7eBjMiA":-1},"/nuxt/ui/2536"]