\n```\n\nsame result is expected when using `active`, but `leadingIcon` is ignored\n```\n\u003CUButton\n label=\"Label\"\n active\n active-color=\"primary\"\n active-variant=\"soft\"\n icon=\"mdi-account\"\n @click.prevent=\"active = !active\"\n/>\n```\n\n### Additional context\n\n\u003Cimg width=\"202\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/0756fb1c-772c-44ae-855d-90aba304bd9e\" />",[2873,2876,2877],{"name":2874,"color":2875},"bug","d73a4a",{"name":2860,"color":2861},{"name":2878,"color":2879},"triage","ffffff",3972,"Different result than static for active-color & active-variant","2025-04-24T15:30:39Z","https://github.com/nuxt/ui/issues/3972",0.72579,{"description":2886,"labels":2887,"number":2895,"owner":2863,"repository":2863,"state":2865,"title":2896,"updated_at":2897,"url":2898,"score":2899},"The error occurs when I go to the third level child page, then back to the second and then go to the page with await inside\r\n\r\nReproduction:\r\n[https://stackblitz.com/edit/nuxt-starter-btlcfb?file=pages%2Fwaiting.vue](https://stackblitz.com/edit/nuxt-starter-btlcfb?file=pages%2Fwaiting.vue)\r\n\r\nInstructions for reproducing the bug:\r\n1. INDEX PAGE must be initial\r\n2. Go to SETTING/PROJECT PAGE\r\n3. Go to SETTING/PROJECT/CREATE PAGE\r\n4. Go to SETTING/PROJECT PAGE\r\n5. Go to WAITING PAGE\r\n6. Look in console (error due to waiting)\r\n\r\nErrors in console:\r\nUncaught (in promise) TypeError: Cannot read properties of null (reading 'namespaceURI')\r\nUncaught (in promise) TypeError: Cannot read properties of null (reading 'exposed')\r\n\u003Cimg width=\"647\" alt=\"image\" src=\"https://github.com/nuxt/nuxt/assets/37239202/6a747fe0-a7cd-41a4-abf7-e2efcd99868b\">\r\n\u003Cimg width=\"648\" alt=\"image\" src=\"https://github.com/nuxt/nuxt/assets/37239202/d9a84a21-2b5c-429e-bd81-f26c24f88c75\">\r\n\r\nThis error was not fixed for more than a month, maybe several\r\n\r\n_Originally posted by @ilyaDegtyarenko in https://github.com/nuxt/nuxt/discussions/23221_",[2888,2889,2892],{"name":2874,"color":2875},{"name":2890,"color":2891},"🔨 p3-minor","FBCA04",{"name":2893,"color":2894},"suspense","C70109",23232,"The error occurs when I go to the third level child page, then back to the second and then go to the page with await inside","2024-11-19T16:20:56Z","https://github.com/nuxt/nuxt/issues/23232",0.73839396,{"description":2901,"labels":2902,"number":2907,"owner":2863,"repository":2864,"state":2908,"title":2909,"updated_at":2910,"url":2911,"score":2912},"### Environment\n\n- Operating System: Darwin\r\n- Node Version: v18.18.2\r\n- Nuxt Version: 3.13.1\r\n- CLI Version: 3.13.1\r\n- Nitro Version: 2.9.7\r\n- Package Manager: bun@1.1.24\r\n- Builder: -\r\n- User Config: devtools, modules, eslint, runtimeConfig, site, mdc, image, components, strapi, i18n, vite, routeRules, formkit, compatibilityDate\r\n- Runtime Modules: @nuxtjs/strapi@1.12.0, @nuxt/image@1.8.0, @vueuse/nuxt@10.11.1, @nuxtjs/i18n@8.5.1, @nuxt/eslint@0.3.13, @nuxt/fonts@0.7.2, @nuxtjs/mdc@0.8.3, @formkit/nuxt@1.6.5, nuxt3-vuex-module@1.1.0, nuxt3-interpolation/index.cjs, nuxt-swiper@1.2.2, nuxt-marquee@1.0.4, @nuxtjs/seo@2.0.0-rc.20, @formkit/nuxt@1.6.5, @nuxt/ui@2.18.4\r\n- Build Modules: -\n\n### Version\n\nv2.18.4\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-dbk9vy?file=app.vue\n\n### Description\n\nEnter transition of sliderover Module not working properly. Instant appearing of elements (with sometimes slight but too quick transitions). Exit transition works fine. \r\n\r\nTried on Chrome, Firefox & Safari on Mac.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2903,2904],{"name":2874,"color":2875},{"name":2905,"color":2906},"upstream","78bddb",2127,"closed","[Slideover/Modal] Enter transition not working","2024-09-20T14:03:47Z","https://github.com/nuxt/ui/issues/2127",0.7057458,{"description":2914,"labels":2915,"number":2921,"owner":2863,"repository":2864,"state":2908,"title":2922,"updated_at":2923,"url":2924,"score":2925},"### 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_",[2916,2919,2920],{"name":2917,"color":2918},"enhancement","a2eeef",{"name":2860,"color":2861},{"name":2878,"color":2879},3225,"Expose close event for USlideover (Overlay & Button)","2025-03-28T17:34:38Z","https://github.com/nuxt/ui/issues/3225",0.70889187,{"description":2927,"labels":2928,"number":2931,"owner":2863,"repository":2864,"state":2908,"title":2932,"updated_at":2933,"url":2934,"score":2935},"### 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",[2929,2930],{"name":2857,"color":2858},{"name":2860,"color":2861},3390,"How to add margins around the Slideover panel?","2025-02-25T15:36:40Z","https://github.com/nuxt/ui/issues/3390",0.7123689,{"description":2937,"labels":2938,"number":2939,"owner":2863,"repository":2940,"state":2908,"title":2941,"updated_at":2942,"url":2943,"score":2944},"Reproduction:\r\nhttps://github.com/QaahirStewart/icontest\r\n\r\nIt seems that when icon name is bounded with access a property ex(.dot after emptyIconData) \u003CIcon :name=\"emptyIconData.logo\" /> this error is getting produced. ",[],217,"icon","Cannot read properties of undefined (reading 'startsWith')","2024-07-28T23:03:04Z","https://github.com/nuxt/icon/issues/217",0.7166509,{"description":2946,"labels":2947,"number":2939,"owner":2863,"repository":2949,"state":2908,"title":2950,"updated_at":2951,"url":2952,"score":2944},"### 🐛 The bug\n\n\r\n\r\nReproducible with 0.7.0 and upwards (due to the new unhead integration)\r\nNot reproducible in 0.6.X and lower\r\n\r\n\r\n\n\n### 🛠️ To reproduce\n\nhttps://stackblitz.com/edit/nuxt-starter-pkwfkx?file=pages%2Findex.vue\n\n### 🌈 Expected behavior\n\nReturn value of `useScript` and others should not be `any`\n\n### ℹ️ Additional context\n\n_No response_",[2948],{"name":2874,"color":2875},"scripts","Return types of `useScript` are `any` since unhead 1.1.0 integration (v0.7)","2024-09-09T18:23:29Z","https://github.com/nuxt/scripts/issues/217",{"description":2954,"labels":2955,"number":2956,"owner":2863,"repository":2957,"state":2908,"title":2958,"updated_at":2959,"url":2960,"score":2961},"- [x] Colors & Fonts\n- [x] Landing page (Home)\n- [x] Showcase categories/hero\n- [x] Modules categories/hero\n- [x] Blog categories/hero\n- [x] Support hero/content",[],1305,"nuxt.com","Marketing Update","2023-07-04T10:00:31Z","https://github.com/nuxt/nuxt.com/issues/1305",0.7192037,{"description":2963,"labels":2964,"number":2968,"owner":2863,"repository":2864,"state":2908,"title":2969,"updated_at":2970,"url":2971,"score":2972},"### 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```",[2965,2966,2967],{"name":2874,"color":2875},{"name":2860,"color":2861},{"name":2878,"color":2879},3719,"Toast does not always dispose","2025-04-02T07:18:01Z","https://github.com/nuxt/ui/issues/3719",0.7246667,["Reactive",2974],{},["Set"],["ShallowReactive",2977],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fNkr-_lcAxy0REEb6hCVtXAaAw0DhQ8DTWxo6VJXcrWw":-1},"/nuxt/ui/2860"]