` component, specifically when the `appear` prop is set.\r\n\r\nIt seems that the click event listener on an element inside `\u003CTransition appear>` isn't being properly handled.\r\nSteps to reproduce:\r\n1. open the reproduction\r\n2. click on the semi-transparent fullscreen div\r\n3. *nothing happens* even though it should have set its visibility to `false`\r\n\r\n1. remove `appear` from the `\u003CTransition>` component in `FullscreenBackground.vue`\r\n2. repeat the same steps & now the click is properly handled\r\n\r\n### Additional context\r\n\r\nI've tried and I couldn't reproduce the same issue in Vue, so I assume it could be a bug in Nuxt.\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3075,3078],{"name":3076,"color":3077},"3.x","29bc7f",{"name":3040,"color":3041},24754,"`\u003CTransition appear>` breaks click event listener","2023-12-15T10:09:43Z","https://github.com/nuxt/nuxt/issues/24754",0.6788463,{"description":3085,"labels":3086,"number":3090,"owner":3029,"repository":3030,"state":3057,"title":3091,"updated_at":3092,"url":3093,"score":3094},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v22.16.0\n- Nuxt Version: 3.17.6\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.13\n- Package Manager: pnpm@10.12.4\n- Builder: -\n- User Config: -\n- Runtime Modules: @nuxt/ui@3.2.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.2.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/serene-river-hypccq\n\n### Description\n\nupdating to 3.2.0, the cancel button does not display\n\n```ts\nconst overlay = useOverlay()\nconst dialog = overlay.create(VDialog, {\n props: {\n showCancelButton: true,\n },\n})\n\nfunction showDialog() {\n dialog.open({\n title: 'Lorem Ipsum',\n description: 'Lorem ipsum dolor sit amet, consectetur adipiscing elit.',\n })\n}\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3087,3088,3089],{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3026,"color":3027},4468,"useOverlay: passing props to open will override the props of the create","2025-07-08T08:51:35Z","https://github.com/nuxt/ui/issues/4468",0.68040854,{"description":3096,"labels":3097,"number":3100,"owner":3029,"repository":3030,"state":3057,"title":3101,"updated_at":3102,"url":3103,"score":3104},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.12.0\n- Nuxt Version: 3.17.3\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: pnpm@8.15.6\n- Builder: -\n- User Config: modules, devtools, compatibilityDate, future, css\n- Runtime Modules: @nuxt/ui@3.1.1\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.1\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/boring-mirzakhani-vjc9wr\n\n### Description\n\nI have a slideover that is opened with `overlay.open` as per documentation. The slideover uses injected values.\n\nIf the injected value is injected in a component that has `UApp` in template, the injection works. If, on the other hand, the injection is done in a component that does not have `UApp` in template, the injection is lost. Workaround would be to add `UApp` to all components doing injections, but there should only be one `UApp`.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3098,3099],{"name":3020,"color":3021},{"name":3023,"color":3024},4209,"Injections from elsewhere than `UApp` pages do not work on overlay components","2025-06-01T13:00:59Z","https://github.com/nuxt/ui/issues/4209",0.68106735,{"description":3106,"labels":3107,"number":3112,"owner":3029,"repository":3029,"state":3057,"title":3113,"updated_at":3114,"url":3115,"score":3116},"### Environment\n\n------------------------------\r\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: yarn@4.4.1\r\n- Builder: -\r\n- User Config: future, srcDir, dir, components, alias, typescript, devtools, modules, routeRules, tailwindcss, postcss, compatibilityDate\r\n- Runtime Modules: @nuxtjs/tailwindcss@6.12.1, @nuxt/image@1.8.0, @nuxt/eslint@0.5.5, @nuxt/content@2.13.2\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nNot working hover events demo: nuxt@3.13.1 + vue@3.5.2\r\nhttps://stackblitz.com/edit/nuxt-vue-3-4-beta-squnun?file=src%2Fpages%2Fhome%2FHomePage.vue,src%2Fshared%2Fui%2Fthumb-carousel%2Fuse-thumb-carousel.ts\r\n\r\nWorking demo: nuxt@3.13.0 + vue@3.4.8\r\nhttps://stackblitz.com/edit/nuxt-vue-3-4-beta-uiqqjl?file=src%2Fpages%2Fhome%2FHomePage.vue,src%2Fshared%2Fui%2Fthumb-carousel%2Fuse-thumb-carousel.ts\r\n\r\nWorking non-nuxt demo: Vite(vike) + vue@3.5.2\r\nhttps://stackblitz.com/edit/dajced?file=pages%2Findex%2F%2BPage.vue,components%2Fthumb-carousel%2Fuse-thumb-carousel.ts\r\n\n\n### Describe the bug\n\n- Open non-working demo\r\n- Wait for the server to start up\r\n- Reload the page (1/twice)\r\n- Hover over the thumbs.\r\n- Navigation should work, but nothing happens, although the carousel itself is initialized\r\n\r\nIn working demos all works fine.\n\n### Additional context\n\nI don't understand what must have been changed in nuxt for my code to stop working.\r\nCan you look at the source code of the `useThumbCarousel` hook that links carousel initialization with expected behavior - maybe there is some part of the code there that causes problems? I'm thinking about watchers or refs.\n\n### Logs\n\n_No response_",[3108,3109],{"name":3040,"color":3041},{"name":3110,"color":3111},"possible regression","B90A42",28856,"Something broken with latest vue (3.5.2+) and latest nuxt (3.13.1)","2024-09-11T19:49:43Z","https://github.com/nuxt/nuxt/issues/28856",0.6843863,{"description":3118,"labels":3119,"number":3122,"owner":3029,"repository":3030,"state":3057,"title":3123,"updated_at":3124,"url":3125,"score":3126},"### Environment\n\n- Operating System: `Linux`\n- Node Version: `v22.2.0`\n- Nuxt Version: `3.17.3`\n- CLI Version: `3.25.1`\n- Nitro Version: `2.11.12`\n- Package Manager: `pnpm@9.4.0`\n- Builder: `-`\n- User Config: `compatibilityDate`, `devtools`, `css`, `vite`, `ui`, `modules`\n- Runtime Modules: `@nuxt/eslint@1.3.1`, `@nuxt/fonts@0.11.4`, `@nuxt/icon@1.12.0`, `@nuxt/image@1.10.0`, `@nuxt/ui@3.1.2`, `@vueuse/nuxt@13.2.0`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.2\n\n### Reproduction\n\n[CodeSanbox here](https://codesandbox.io/p/devbox/nuxt-ui3-n3sxks)\n\nMove the slider, open the console, the `change` event fired does not include the new value of the slider.\n\n### Description\n\nAs explained in the title and reproduction, I'm using the Slider and would like to intercept the `change` event and access the new value. The event is emited correctly but there is no value in it, `event.target` is set to `null`.\n\nI'm not really sure where the issue lies precisely since the underlying RekaUI slider seems to correctly emit a `valueCommit` event with the correct value (according to the vue devtools timeline anyway), and the Slider from Nuxt UI, at least in its source [here](https://github.com/nuxt/ui/blob/d29e1481f2dbaeae196a44b2c084160186e88f47/src/runtime/components/Slider.vue#L100) should be binding this value to the `change` event it emits.\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3120,3121],{"name":3020,"color":3021},{"name":3023,"color":3024},4164,"Slider `change` event does not include value","2025-05-23T13:23:18Z","https://github.com/nuxt/ui/issues/4164",0.69347894,{"description":3128,"labels":3129,"number":3134,"owner":3029,"repository":3030,"state":3057,"title":3135,"updated_at":3136,"url":3137,"score":3138},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v20.18.0\n- Nuxt Version: 3.11.2\n- CLI Version: 3.15.0\n- Nitro Version: 2.9.6\n- Package Manager: pnpm@9.5.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxtjs/i18n@8.0.0, @nuxt/ui@2.16.0, @nuxtjs/tailwindcss@6.12.0, @pinia/nuxt@0.5.1, @nuxtjs/google-fonts@3.2.0, @nuxtjs/eslint-module@4.1.0, @nuxt/test-utils/module@3.13.1\n- Build Modules: -\n------------------------------\n\n\n\n### Version\n\nv.2.15.0\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-1f7znf?file=app.vue,nuxt.config.ts\n\n### Description\n\nWhen providing custom animations through tailwindcss config, some Nuxt UI animations stop working. I have provided an example of a `UButton` with `loading` set in the repro link above.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3130,3131,3132,3133],{"name":3020,"color":3021},{"name":3026,"color":3027},{"name":3052,"color":3053},{"name":3055,"color":3053},2732,"Adding custom animations disable Nuxt UI ones","2025-06-18T09:05:37Z","https://github.com/nuxt/ui/issues/2732",0.6939542,["Reactive",3140],{},["Set"],["ShallowReactive",3143],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f7PwzOStWhUzf0myOgEbVE6cjguH53Mf94l-LeGYP1fo":-1},"/nuxt/ui/4135"]