` 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_",[2910,2913],{"name":2911,"color":2912},"3.x","29bc7f",{"name":2877,"color":2878},24754,"`\u003CTransition appear>` breaks click event listener","2023-12-15T10:09:43Z","https://github.com/nuxt/nuxt/issues/24754",0.6788463,{"description":2920,"labels":2921,"number":2924,"owner":2866,"repository":2867,"state":2902,"title":2925,"updated_at":2926,"url":2927,"score":2928},"### 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```",[2922,2923],{"name":2857,"color":2858},{"name":2860,"color":2861},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.6810674,{"description":2930,"labels":2931,"number":2936,"owner":2866,"repository":2866,"state":2902,"title":2937,"updated_at":2938,"url":2939,"score":2940},"### 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_",[2932,2933],{"name":2877,"color":2878},{"name":2934,"color":2935},"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.6843864,{"description":2942,"labels":2943,"number":2946,"owner":2866,"repository":2867,"state":2902,"title":2947,"updated_at":2948,"url":2949,"score":2950},"### 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```",[2944,2945],{"name":2857,"color":2858},{"name":2860,"color":2861},4164,"Slider `change` event does not include value","2025-05-23T13:23:18Z","https://github.com/nuxt/ui/issues/4164",0.69347894,{"description":2952,"labels":2953,"number":2959,"owner":2866,"repository":2866,"state":2902,"title":2960,"updated_at":2961,"url":2962,"score":2963},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v20.11.1`\r\n- Nuxt Version: `3.11.2`\r\n- CLI Version: `3.11.1`\r\n- Nitro Version: `2.9.6`\r\n- Package Manager: `yarn@4.2.2`\r\n- Builder: `-`\r\n- User Config: `devtools`, `debug`, `hooks`, `modules`, `plugins`, `nitro`, `runtimeConfig`, `dayjs`, `postcss`, `app`, `css`, `apollo`, `carousel`, `tour`, `vue`, `routeRules`\r\n- Runtime Modules: `@nuxtjs/tailwindcss@6.12.0`, `@nuxtjs/device@3.1.1`, `@nuxt/image@1.4.0`, `@pinia/nuxt@0.5.1`, `@pinia-plugin-persistedstate/nuxt@1.2.0`, `dayjs-nuxt@2.1.9`, `vue3-carousel-nuxt@1.1.1`, `@nuxtjs/apollo@5.0.0-alpha.14`, `nuxt-tour@0.0.9`, `@nuxtjs/i18n@8.3.1`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nCannot reproduce the issue either on new repo or stackblitz\r\n\r\nUsing \r\n\r\n \"nuxt\": \"^3.11.2\",\r\n \"@nuxtjs/tailwindcss\": \"^6.12.0\",\n\n### Describe the bug\n\nIn the below image in nuxt 3 bg-transparent is added at last but it is overridden by bg-yocket-neutral-100\r\n\r\n\u003Cimg width=\"647\" alt=\"Screenshot 2024-05-28 at 5 46 06 PM\" src=\"https://github.com/nuxt/nuxt/assets/45727492/081685a9-7c97-4f4e-8449-e3f0bfbc0719\">\r\n\r\nIn nuxt 2 the behaviour was opposite\r\n\u003Cimg width=\"1115\" alt=\"Screenshot 2024-05-28 at 5 52 22 PM\" src=\"https://github.com/nuxt/nuxt/assets/45727492/f4d6d5f5-d323-4312-bb37-46a4fb52f776\">\r\n\r\n\r\nThis same thing is happening throughout the project\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2954,2955,2956],{"name":2911,"color":2912},{"name":2877,"color":2878},{"name":2957,"color":2958},"needs reproduction","FBCA04",27385,"Tailwindcss added at last is not applied","2024-05-30T05:43:05Z","https://github.com/nuxt/nuxt/issues/27385",0.69698495,{"description":2965,"labels":2966,"number":2970,"owner":2866,"repository":2866,"state":2902,"title":2971,"updated_at":2972,"url":2973,"score":2974},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v21.1.0`\r\n- Nuxt Version: `3.10.2`\r\n- CLI Version: `3.10.1`\r\n- Nitro Version: `2.8.1`\r\n- Package Manager: `npm@10.2.0`\r\n- Builder: `-`\r\n- User Config: `ssr`, `target`, `experimental`, `app`, `vue`, `css`, `modules`, `storyblok`, `build`, `vite`, `nitro`, `hooks`, `routeRules`, `imports`, `runtimeConfig`, `devtools`\r\n- Runtime Modules: `@storyblok/nuxt@6.0.4`, `@pinia/nuxt@0.5.1`\r\n- Build Modules: `-`\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-prqbf9?file=app.vue\n\n### Describe the bug\n\nIf you use a `nuxt-link` with the `custom` and `external` prop and click on it, a console.error will occur complaing about the nuxt-link not having the external prop set to true, even though it is.\r\n\r\nThe navigation itself still works, its just a console.error that occurs before you leave the page.\r\n\r\nThe interesting part is that the `replace` prop is respected, but not `external`.\n\n### Additional context\n\nI think the issue is coming from this file:\r\nhttps://github.com/nuxt/nuxt/blob/9326b7a8bde1ae793ba046f7dacc4ebbe200b786/packages/nuxt/src/app/components/nuxt-link.ts#L357C15-L357C23\r\n\r\nThe replace prop is included here, but not external.\n\n### Logs\n\n_No response_",[2967,2968],{"name":2911,"color":2912},{"name":2969,"color":2958},"🔨 p3-minor",25866,"The `nuxt-link` component does not respect the external prop","2024-02-21T21:20:15Z","https://github.com/nuxt/nuxt/issues/25866",0.6976189,["Reactive",2976],{},["Set"],["ShallowReactive",2979],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f7PwzOStWhUzf0myOgEbVE6cjguH53Mf94l-LeGYP1fo":-1},"/nuxt/ui/4135"]