`\n\nit doesn't work that way\n\nI really ask for help!",[2001,2002],{"name":1985,"color":1986},{"name":1988,"color":1989},3098,"Table filtered, sorting fetch","2025-01-14T11:05:37Z","https://github.com/nuxt/ui/issues/3098",0.6600957,{"description":2009,"labels":2010,"number":2013,"owner":1991,"repository":1992,"state":1993,"title":2014,"updated_at":2015,"url":2016,"score":2017},"### 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",[2011,2012],{"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.6723312,{"description":2019,"labels":2020,"number":2025,"owner":1991,"repository":1992,"state":1993,"title":2026,"updated_at":2027,"url":2028,"score":2029},"### Description\n\nI wanted to do something like the inline field label shown in the component examples in the docs, but couldn't find a suitable builtin. I think it's a nice halfway between MD's label-in-the-field strategy and while I could abuse the `leading` slot of the input, I think it makes more sense to be generic across input types. \n\n\n\nI did end up copy/pasting the source but it would be cool if the FormField (or something) had an `inline` variant that did this.\n\nFor reference:\nhttps://github.com/nuxt/ui/blob/50d68a636cc8b260dd3b8cf8afecb3b564b9d75d/docs/app/components/content/ComponentExample.vue#L162-L167\n\nThanks for your consideration 😄 \n\n### Additional context\n\n_No response_",[2021,2024],{"name":2022,"color":2023},"enhancement","a2eeef",{"name":1988,"color":1989},3543,"Inline Form Field Label","2025-03-14T11:13:49Z","https://github.com/nuxt/ui/issues/3543",0.68258834,{"description":2031,"labels":2032,"number":2038,"owner":1991,"repository":1992,"state":1993,"title":2039,"updated_at":2040,"url":2041,"score":2042},"### Description\n\n### Feature Request: Add `variant` and `status-position` props to `UProgress` component\n\n#### Description\nI’m a junior developer, and I’ve been working on enhancing the flexibility of the `Progress` component by adding two new props: `variant` and `status-position`. These props allow for better customization, especially when using the `Progress` component in different design contexts.\n\n- **`variant`**: This prop allows you to choose between two styles for the progress bar: `linear` and `circular`. The `circular` variant provides a circular progress bar instead of the default linear style.\n \n- **`status-position`**: This prop controls the position of the progress status (the percentage or label) relative to the progress bar. The possible values are:\n - `inside`: The status is displayed inside the circle (for the `circular` variant).\n - `outside`: The status is displayed outside the circle.\n\n#### Motivation\nThis update would help in using the `Progress` component more flexibly across different layouts, providing options for both linear and circular progress indicators with customizable label placements.\n\n#### What I've Done\nI’m still a junior developer, so the implementation is not perfect, but a good portion of the work is done. I’ve added the `variant` and `status-position` props to the `Progress` component. I’d love to know if this is something you’d like to integrate into the main repository and whether I can open a pull request for it.\n\n#### Additional Notes\n- The `variant` prop accepts values `linear` or `circular`.\n- The `status-position` prop accepts values `inside` or `outside`.\n \nWould love to hear your thoughts on this approach!\n\n\n### Additional context\n\n[Reka UI : Progress Circular](https://reka-ui.com/examples/progress-circular)",[2033,2034,2035],{"name":2022,"color":2023},{"name":1988,"color":1989},{"name":2036,"color":2037},"triage","ffffff",3728,"[UProgress]: Add `variant` and `status-position` props","2025-03-29T14:31:22Z","https://github.com/nuxt/ui/issues/3728",0.6841515,{"description":2044,"labels":2045,"number":2048,"owner":1991,"repository":1992,"state":1993,"title":2049,"updated_at":2050,"url":2051,"score":2052},"### Description\n\nHi, I'm having a hard time applying transition to dark / light background.\n\nMy `main.css` file is as follows.\n\nChanging the background color from `slate` to `stone`, for example, works fine.\n\nThe problem is just for the light / dark theme transition.\n\n```\n:root {\n --ui-bg: var(--ui-color-neutral-100);\n}\n\n.dark {\n --ui-bg: var(--ui-color-neutral-900);\n}\n\n@layer base {\n body {\n @apply transition-colors duration-1000;\n }\n}\n```\n\nHere is the function that changes the theme:\n\n```\nconst isDark = computed({\n get() {\n return colorMode.value === 'dark';\n },\n set() {\n colorMode.preference = colorMode.value === 'dark' ? 'light' : 'dark';\n },\n});\n```\n\nAny help would be appreciated, thanks!\n",[2046,2047],{"name":1985,"color":1986},{"name":1988,"color":1989},3645,"Applying transition-colors to light / dark theme","2025-03-21T16:20:57Z","https://github.com/nuxt/ui/issues/3645",0.687921,{"description":2054,"labels":2055,"number":2059,"owner":1991,"repository":1992,"state":2060,"title":2061,"updated_at":2062,"url":2063,"score":2064},"### 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_",[2056,2057,2058],{"name":2022,"color":2023},{"name":1988,"color":1989},{"name":2036,"color":2037},3225,"closed","Expose close event for USlideover (Overlay & Button)","2025-03-28T17:34:38Z","https://github.com/nuxt/ui/issues/3225",0.6230067,{"description":2066,"labels":2067,"number":2071,"owner":1991,"repository":1992,"state":2060,"title":2072,"updated_at":2073,"url":2074,"score":2075},"### 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_",[2068],{"name":2069,"color":2070},"bug","d73a4a",2086,"SelectMenu ignoring initial object values","2024-11-12T17:12:26Z","https://github.com/nuxt/ui/issues/2086",0.65378654,{"description":2077,"labels":2078,"number":2081,"owner":1991,"repository":1992,"state":2060,"title":2082,"updated_at":2083,"url":2084,"score":2085},"### 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",[2079,2080],{"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.672204,{"description":2087,"labels":2088,"number":2092,"owner":1991,"repository":1992,"state":2060,"title":2093,"updated_at":2094,"url":2095,"score":2096},"### 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_",[2089,2090],{"name":2022,"color":2023},{"name":2091,"color":2037},"wontfix-v2",2737,"Specify a components variant for each color mode.","2025-03-03T22:31:17Z","https://github.com/nuxt/ui/issues/2737",0.673561,["Reactive",2098],{},["Set"],["ShallowReactive",2101],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"PimGAYeX5cAZQbI3s69kNspPm0ZtRczftNgbO7Ruu1k":-1},"/nuxt/ui/3719"]