` 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_",[2909,2912],{"name":2910,"color":2911},"3.x","29bc7f",{"name":2888,"color":2889},24754,"`\u003CTransition appear>` breaks click event listener","2023-12-15T10:09:43Z","https://github.com/nuxt/nuxt/issues/24754",0.70380455,{"description":2919,"labels":2920,"number":2926,"owner":2877,"repository":2878,"state":2901,"title":2927,"updated_at":2928,"url":2929,"score":2930},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.11.1\n- Nuxt Version: 3.16.2\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: npm@10.2.4\n- Builder: -\n- User Config: css, compatibilityDate, devtools, future, modules, runtimeConfig, ssr, typescript\n- Runtime Modules: @nuxt/eslint@1.4.0, @nuxt/fonts@0.11.4, @nuxt/ui-pro@3.1.2, @pinia/nuxt@0.5.5, @vueuse/nuxt@10.11.1, nuxt-auth-utils@0.5.20, nuxt-authorization@0.3.4\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.2\n\n### Reproduction\n\nJust use the code of https://github.com/nuxt-ui-pro/dashboard/blob/main/app/pages/settings.vue and add a child to one of the links used for the UNavigationMenu. Like :\n````\n{\n label: \"General\",\n icon: \"i-lucide-user\",\n to: \"/settings\",\n children: [\n {\n label: \"Hello\",\n icon: \"i-lucide-book-open\",\n },\n ],\n exact: true,\n },\n````\n\n### Description\n\nIt seems wrapping the UNavigationMenu component in UDashboardToolbar will cause the UNavigationMenu's links children dropdown to not appear or be hidden.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2921,2922,2923],{"name":2868,"color":2869},{"name":2871,"color":2872},{"name":2924,"color":2925},"nuxt/ui-pro","00dc82",4177,"UNavigationMenu item children not visible when wrapped in UDashboardToolbar","2025-05-23T12:23:17Z","https://github.com/nuxt/ui/issues/4177",0.71200246,{"description":2932,"labels":2933,"number":2936,"owner":2877,"repository":2878,"state":2901,"title":2937,"updated_at":2938,"url":2939,"score":2940},"### Environment\n\n\"@vueuse/nuxt\": \"^13.1.0\"\n\"@nuxt/ui\": \"^3.1.2\"\nnode: lts/jod (22.11.0)\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.2\n\n### Reproduction\n\n\n\n\n\n### Description\n\nWhen using the UTab component with the variant=\"link\", applying custom CSS classes to enable horizontal scrolling (e.g., overflow-x: auto; or equivalent utility classes) causes the visual style indicating the currently active tab to be lost or overridden.\n\n```js\n{\n variant: 'link',\n ui: {\n list: 'bg-white overflow-x-auto overflow-y-hidden',\n trigger: 'min-w-auto'\n }\n}\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2934,2935],{"name":2868,"color":2869},{"name":2871,"color":2872},4198,"UTabs style issue","2025-05-23T13:23:24Z","https://github.com/nuxt/ui/issues/4198",0.7138786,{"description":2942,"labels":2943,"number":2947,"owner":2877,"repository":2878,"state":2901,"title":2948,"updated_at":2949,"url":2950,"score":2951},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.10.0\n- Nuxt Version: 3.16.2\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.9\n- Package Manager: npm@10.9.0\n- Builder: -\n- User Config: nitro, build, compatibilityDate, devtools, ssr, css, modules, i18n\n- Runtime Modules: @nuxt/ui@3.1.0, @nuxt/test-utils@3.17.2, @nuxt/image@1.10.0, @nuxt/icon@1.12.0, @nuxt/fonts@0.11.2, @nuxt/eslint@1.3.0, @nuxtjs/i18n@9.5.3, @nuxtjs/leaflet@1.2.6, @pinia/nuxt@0.11.0\n- Build Modules: -\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.16.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/fancy-river-42j5xw?workspaceId=ws_GgeGxunRZmD7bdWXHYL2Xk\n\n### Description\n\nWhile the `USlideOver` is active, it is not possible to interact with the background elements, even if `:overlay=\"false\"`. This seems counter-intuitive and [formerly classified as a bug in v2](https://github.com/nuxt/ui/issues/1402#issuecomment-2872304863).\n\n### Additional context\n\ntested with both 3.1.1 and 3.1.0\n\nA workaround is setting `\"pointer-events: auto\"` in the background element styles, which seems to enable all pointer events.\n\n### Logs\n\n```shell-script\n\n```",[2944,2945,2946],{"name":2868,"color":2869},{"name":2871,"color":2872},{"name":2874,"color":2875},4135,"Slideover blocks background interaction even with `overlay=false`","2025-05-13T12:59:56Z","https://github.com/nuxt/ui/issues/4135",0.71406144,{"labels":2953,"number":2960,"owner":2877,"repository":2877,"state":2901,"title":2961,"updated_at":2962,"url":2963,"score":2964},[2954,2956,2957],{"name":2955,"color":2875},"stale",{"name":2888,"color":2889},{"name":2958,"color":2959},"2.x","d4c5f9",10165,"Nuxt is removing universal selectors from css","2023-01-22T15:45:12Z","https://github.com/nuxt/nuxt/issues/10165",0.7144007,{"description":2966,"labels":2967,"number":2970,"owner":2877,"repository":2877,"state":2901,"title":2971,"updated_at":2972,"url":2973,"score":2974},"### Environment\n\n- Operating System: Windows 10\r\n- Node Version: v20.9.0\r\n- Nuxt Version: 3.8.2\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: yarn@1.22.21\r\n- Builder: -\r\n- User Config: routeRules, devtools, css, runtimeConfig, nitro, modules, alias, vite, components\r\n- Runtime Modules: @nuxtjs/i18n@8.0.0-rc.5, nuxt-icons@3.2.1, @unocss/nuxt@0.57.7, @element-plus/nuxt@1.0.7, @vueuse/nuxt@10.7.0, @vueuse/motion/nuxt@2.0.0, @pinia/nuxt@0.5.1, @pinia-plugin-persistedstate/nuxt@1.2.0, @nuxtjs/device@3.1.1\r\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-rr4shs?file=app.vue\n\n### Describe the bug\n\nIn the dark mode && toggleDark from @vueuse/core, refresh the page, we would see the background color of the page flashes from white to black. \n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2968,2969],{"name":2910,"color":2911},{"name":2888,"color":2889},24819,"Background color flashes between light and dark mode using @vueuse/nuxt","2023-12-20T03:49:21Z","https://github.com/nuxt/nuxt/issues/24819",0.7191757,{"description":2976,"labels":2977,"number":2979,"owner":2877,"repository":2877,"state":2901,"title":2980,"updated_at":2981,"url":2982,"score":2983},"I just discovered the most annoying bug on Earth, guys. I spend 30 minutes to figuring out why my layout looks strange (transparent rectangle around text). Then I saw this\r\n\r\n```\r\n.main-content-wrapper\r\n transition: background-color .75s;\r\n backface-visibility: hidden;\r\n will-change: background-color;\r\n```\r\n\r\nMy original code doesn't have this `backface-visibility: hidden`!!!\r\nWhy Nuxt adds it? Both in Dev and after build. \n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1677\">#c1677\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2978],{"name":2958,"color":2959},1867,"Why Nuxt adds backface-visibility: hidden?","2023-01-18T15:42:46Z","https://github.com/nuxt/nuxt/issues/1867",0.7237332,["Reactive",2985],{},["Set"],["ShallowReactive",2988],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$faXb5XbFd77za-5VUzLIhacoW5z2V5RBFJIFw2t0Za-I":-1},"/nuxt/ui/4204"]