`\n\nit doesn't work that way\n\nI really ask for help!",[2011,2012],{"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.6840782,{"description":2019,"labels":2020,"number":2023,"owner":1991,"repository":1992,"state":2024,"title":2025,"updated_at":2026,"url":2027,"score":2028},"### 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",[2021,2022],{"name":1985,"color":1986},{"name":1988,"color":1989},3390,"closed","How to add margins around the Slideover panel?","2025-02-25T15:36:40Z","https://github.com/nuxt/ui/issues/3390",0.6706435,{"description":2030,"labels":2031,"number":2035,"owner":1991,"repository":1992,"state":2024,"title":2036,"updated_at":2037,"url":2038,"score":2039},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v20.10.0\n- Nuxt Version: 3.13.2\n- CLI Version: 3.15.0\n- Nitro Version: 2.9.7\n- Package Manager: yarn@4.3.0\n- Builder: -\n- User Config: default\n- Runtime Modules: -\n- Build Modules: -\n\n### Version\n\n2.18.7\n\n### Reproduction\n\nPut a tooltip with an icon within the `\u003Ctemplate #trailing>` slot.\n\n### Description\n\nIf an element in an input's \"trailing\" slot is wrapped in the tooltip component, it doesn't show the tooltip when hovered/clicked.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2032],{"name":2033,"color":2034},"bug","d73a4a",2461,"Tooltip in \"trailing\" slot of input deosn't work.","2024-10-25T15:26:45Z","https://github.com/nuxt/ui/issues/2461",0.6745477,{"description":2041,"labels":2042,"number":2048,"owner":1991,"repository":1992,"state":2024,"title":2049,"updated_at":2050,"url":2051,"score":2052},"### 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```",[2043,2044,2045],{"name":2033,"color":2034},{"name":1988,"color":1989},{"name":2046,"color":2047},"triage","ffffff",3719,"Toast does not always dispose","2025-04-02T07:18:01Z","https://github.com/nuxt/ui/issues/3719",0.6783346,{"description":2054,"labels":2055,"number":2061,"owner":1991,"repository":1992,"state":2024,"title":2062,"updated_at":2063,"url":2064,"score":2065},"### 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,2059,2060],{"name":2057,"color":2058},"enhancement","a2eeef",{"name":1988,"color":1989},{"name":2046,"color":2047},3225,"Expose close event for USlideover (Overlay & Button)","2025-03-28T17:34:38Z","https://github.com/nuxt/ui/issues/3225",0.68687266,{"description":2067,"labels":2068,"number":2078,"owner":1991,"repository":1992,"state":2024,"title":2079,"updated_at":2080,"url":2081,"score":2082},"### 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```",[2069,2070,2073,2074,2075],{"name":2033,"color":2034},{"name":2071,"color":2072},"needs reproduction","CB47CF",{"name":1988,"color":1989},{"name":2046,"color":2047},{"name":2076,"color":2077},"closed-by-bot","ededed",3303,"open Popover manually","2025-03-25T02:04:46Z","https://github.com/nuxt/ui/issues/3303",0.68947214,{"description":2084,"labels":2085,"number":2088,"owner":1991,"repository":1992,"state":2024,"title":2089,"updated_at":2090,"url":2091,"score":2092},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.4.0\n- Nuxt Version: 3.14.159\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.13.2\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.8\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.8\n\n### Reproduction\n\n-\n\n### Description\n\nDefault classes of container in [docs](https://ui3.nuxt.dev/components/container#theme) is:\n```ts\nexport default defineAppConfig({\n ui: {\n container: {\n base: 'max-w-[var(--ui-container)] mx-auto px-4 sm:px-6 lg:px-8'\n }\n }\n})\n```\n**But no one of classes except `mx-auto` is not was created.**\nI change `--ui-container` variable like in [docs](https://ui3.nuxt.dev/getting-started/theme#container):\n```css\n/** app.css */\n\n@import 'tailwindcss';\n@import '@nuxt/ui';\n\n@theme {\n --container-xl: 1280px;\n}\n\n:root {\n --ui-container: var(--container-xl);\n}\n```\nAs result, container classes is `max-w-7xl mx-auto px-4 sm:px-6 lg:px-8` and still not was created, except `mx-auto`.\n\nBut if i create `app.config.ts`:\n```ts\nexport default defineAppConfig({\n ui: {\n container: {\n base: 'max-w-[var(--ui-container)] mx-auto px-4 sm:px-6 lg:px-8'\n }\n }\n})\n```\nAll is ok, width and other classes are created and applying.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2086,2087],{"name":2033,"color":2034},{"name":1988,"color":1989},2655,"Classes of container component are not working properly","2024-11-16T13:13:33Z","https://github.com/nuxt/ui/issues/2655",0.69544345,{"description":2094,"labels":2095,"number":2097,"owner":1991,"repository":1992,"state":2024,"title":2098,"updated_at":2099,"url":2100,"score":2101},"### Description\r\n\r\nHello !\r\n\r\nThis module is amazing, thanks a lot for this.\r\nI just started using nuxthub, and while reading the logs, I found components names I don't use. Are all the components built ? If yes, is it possible to exclude from build the unused components ?\r\n\r\nThanks !\r\nCheers from France !\r\n\r\nEdit : by reading my nuxt.config again, I see I defined these lines : \r\n\r\n```\r\n ui: {\r\n global: true,\r\n },\r\n components: {\r\n global: true,\r\n dirs: ['~/components']\r\n },\r\n```\r\n\r\nIs it the reason why all the UI components are built, even if I don't use them ? I don't remember why I decided to make everything global, but I'm sure I don't understand this option 🥇 \r\n\r\nEdit2 : Ok, this was indeed the `global: true` options that made all the ui components built, sorry for this silly question !",[2096],{"name":1985,"color":1986},2174,"Are all the components built during build process ?","2024-09-11T00:08:50Z","https://github.com/nuxt/ui/issues/2174",0.7048166,["Reactive",2103],{},["Set"],["ShallowReactive",2106],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"8exWf8GvxGvPKxEJjscAacEkQKu0CF7QOT7Oho1X_iw":-1},"/nuxt/ui/2737"]