\n\nI updated to Nuxt UI 3 and deployed it on June 30, and from the next day onwards, my rankings have plummeted.\n\n\u003Cimg width=\"1340\" height=\"395\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/4f1af322-2237-4f74-853a-6c7fa6b7fd9e\" />\n\n\u003Cimg width=\"458\" height=\"385\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/273c66c7-333f-413f-9deb-435d2c293efa\" />\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3034,3037,3040],{"name":3035,"color":3036},"bug","d73a4a",{"name":3038,"color":3039},"v3","49DCB8",{"name":3041,"color":3042},"triage","ffffff",4507,"ui","Significant SEO and LCP Performance Drop After Updating to Nuxt UI 3","2025-07-11T18:09:12Z","https://github.com/nuxt/ui/issues/4507",0.7353093,{"description":3050,"labels":3051,"number":3059,"owner":3025,"repository":3044,"state":3060,"title":3061,"updated_at":3062,"url":3063,"score":3064},"### Environment\n\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.14.159\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@2.19.2\n- Build Modules: -\n\n### Version\n\n2.19.2\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-kft69t?file=README.md\n\nLive: https://rad-fudge-8ff161.netlify.app/\n\n### Description\n\nSo this is a safari mobile bug only! About the UCarousel. \n\nWhen testing on desktop make sure you change the User Agent to Iphone in Safari. \n\nThe active slide/page is a bit random. You can reproduce by refreshing the page. Sometimes it starts at index 0 but other times at 3 etc. \n\nI tried to make a workaround in the onMounted. But that also does not seems to work. \n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3052,3053,3054,3057],{"name":3035,"color":3036},{"name":3041,"color":3042},{"name":3055,"color":3056},"closed-by-bot","ededed",{"name":3058,"color":3056},"stale",2683,"closed","UCarousel Safari (Mobile only) bug","2025-06-18T09:05:47Z","https://github.com/nuxt/ui/issues/2683",0.6737098,{"description":3066,"labels":3067,"number":3071,"owner":3025,"repository":3044,"state":3060,"title":3072,"updated_at":3073,"url":3074,"score":3075},"### 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```",[3068,3069,3070],{"name":3035,"color":3036},{"name":3038,"color":3039},{"name":3041,"color":3042},4135,"Slideover blocks background interaction even with `overlay=false`","2025-05-13T12:59:56Z","https://github.com/nuxt/ui/issues/4135",0.69824255,{"description":3077,"labels":3078,"number":3082,"owner":3025,"repository":3044,"state":3060,"title":3083,"updated_at":3084,"url":3085,"score":3086},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: ^3.17.5\n- CLI Version: 3.25.1\n- Nitro Version: -\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: devtools, modules, css, future, compatibilityDate, formkit\n- Runtime Modules: @nuxt/ui@^3.1.3, @nuxt/eslint@^1.4.1, @formkit/nuxt@^1.6.9\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.3\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/gallant-scooby-hcy72z\n\n### Description\n\nI am upgrading my app to use Nuxt UI v3 and am having issues with `UModal` and [FormKit](https://formkit.com/).\n\nI am unable to open a modal with a FormKit modal inside of it. I get the following error.\n\n\u003Cimg width=\"557\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/dc0baba8-ed91-4006-9164-5e9e1fa6c67a\" />\n\nI believe this is an issue with Nuxt UI and not FormKit because it used to work fine on the previous version.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nindex.vue:17 [Vue warn]: Unhandled error during execution of mounted hook \n at \u003CDialogTrigger key=0 as-child=\"\" class=\"\" > \n at \u003CDialogRoot modal=true open=true onAfter:leave=fn ... > \n at \u003CUModal close= {onClick: ƒ} title=\"This modal was opened programmatically 0 times\" open=true ... > \n at \u003CModalExample key= Symbol(useOverlay) ref_for=true count=0 ... > \n at \u003CUOverlayProvider > \n at \u003CTooltipProvider > \n at \u003CConfigProvider use-id=fn\u003Cuse-id> dir=undefined locale=undefined > \n at \u003CApp > \n at \u003CApp key=4 > \n at \u003CNuxtRoot>\nwarn$1 @ runtime-core.esm-bundler.js?v=fb91d406:50\nlogError @ runtime-core.esm-bundler.js?v=fb91d406:261\nhandleError @ runtime-core.esm-bundler.js?v=fb91d406:253\ncallWithErrorHandling @ runtime-core.esm-bundler.js?v=fb91d406:199\ncallWithAsyncErrorHandling @ runtime-core.esm-bundler.js?v=fb91d406:204\nhook.__weh.hook.__weh @ runtime-core.esm-bundler.js?v=fb91d406:2842\nflushPostFlushCbs @ runtime-core.esm-bundler.js?v=fb91d406:382\nflushJobs @ runtime-core.esm-bundler.js?v=fb91d406:424\nPromise.then\nqueueFlush @ runtime-core.esm-bundler.js?v=fb91d406:319\nqueueJob @ runtime-core.esm-bundler.js?v=fb91d406:314\neffect2.scheduler @ runtime-core.esm-bundler.js?v=fb91d406:5499\ntrigger @ reactivity.esm-bundler.js?v=fb91d406:235\nendBatch @ reactivity.esm-bundler.js?v=fb91d406:293\ntrigger @ reactivity.esm-bundler.js?v=fb91d406:693\nset @ reactivity.esm-bundler.js?v=fb91d406:974\nopen @ useOverlay.js?v=fb91d406:29\nopen @ useOverlay.js?v=fb91d406:18\nopen @ index.vue:17\n(anonymous) @ Button.vue:80\nonClickWrapper @ Button.vue:80\nonClickWrapper @ LinkBase.vue:30\ncallWithErrorHandling @ runtime-core.esm-bundler.js?v=fb91d406:197\ncallWithAsyncErrorHandling @ runtime-core.esm-bundler.js?v=fb91d406:204\ninvoker @ runtime-dom.esm-bundler.js?v=fb91d406:720\nuseForwardExpose.js?v=fb91d406:8 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'nodeName')\n at ComputedRefImpl.fn (useForwardExpose.js?v=fb91d406:8:64)\n at refreshComputed (reactivity.esm-bundler.js?v=fb91d406:361:29)\n at get value (reactivity.esm-bundler.js?v=fb91d406:1567:5)\n at DialogTrigger.js?v=fb91d406:19:57\n at runtime-core.esm-bundler.js?v=fb91d406:2862:40\n at callWithErrorHandling (runtime-core.esm-bundler.js?v=fb91d406:197:19)\n at callWithAsyncErrorHandling (runtime-core.esm-bundler.js?v=fb91d406:204:17)\n at hook.__weh.hook.__weh (runtime-core.esm-bundler.js?v=fb91d406:2842:19)\n at flushPostFlushCbs (runtime-core.esm-bundler.js?v=fb91d406:382:28)\n at flushJobs (runtime-core.esm-bundler.js?v=fb91d406:424:5)\n```",[3079,3080,3081],{"name":3035,"color":3036},{"name":3038,"color":3039},{"name":3041,"color":3042},4309,"UModal does not work with FormKit","2025-06-07T23:36:34Z","https://github.com/nuxt/ui/issues/4309",0.7001981,{"labels":3088,"number":3092,"owner":3025,"repository":3025,"state":3060,"title":3093,"updated_at":3094,"url":3095,"score":3096},[3089],{"name":3090,"color":3091},"2.x","d4c5f9",6589,"question for nuxt transition","2023-01-18T21:49:17Z","https://github.com/nuxt/nuxt/issues/6589",0.723936,{"description":3098,"labels":3099,"number":3103,"owner":3025,"repository":3044,"state":3060,"title":3104,"updated_at":3105,"url":3106,"score":3107},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.20.3\r\n- Nuxt Version: 3.12.1\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.6\r\n- Package Manager: pnpm@8.15.6\r\n- Builder: -\r\n- User Config: modules\r\n- Runtime Modules: @nuxt/ui@2.17.0\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Version\r\n\r\nv2.17.0\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-ui-5movd8?file=app.vue\r\n(Test on mobile or open Devtools and toggle device mode.)\r\n\r\n### Description\r\n\r\nWhen two or more `UModal` are using `preventClose` prop doesn't allow to interact with the elements of the modal on top when in touch mode.\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3100,3101,3102],{"name":3035,"color":3036},{"name":3055,"color":3056},{"name":3058,"color":3056},1932,"`UModal` preventClose doesn't allow to interact with elements","2025-06-19T02:12:17Z","https://github.com/nuxt/ui/issues/1932",0.7248361,{"labels":3109,"number":3114,"owner":3025,"repository":3025,"state":3060,"title":3115,"updated_at":3116,"url":3117,"score":3118},[3110,3113],{"name":3111,"color":3112},"3.x","29bc7f",{"name":3019,"color":3020},14567,"Can you spend more time on finishing framework, not on starting splash screen","2023-01-19T17:37:11Z","https://github.com/nuxt/nuxt/issues/14567",0.7265744,{"description":3120,"labels":3121,"number":3125,"owner":3025,"repository":3044,"state":3060,"title":3126,"updated_at":3127,"url":3128,"score":3129},"### Environment\n\nOperating System: Linux\nNode Version: v18.20.3\nNuxt Version: 3.15.4\nCLI Version: 3.21.1\nNitro Version: 2.10.4\nPackage Manager: pnpm@8.15.6\nBuilder: -\nUser Config: modules\nRuntime Modules: @nuxt/ui@2.21.0\nBuild Modules: -\n\n\n### Version\n\n^2.17.0\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-um7dcx8a?file=app.vue\n\n### Description\n\nIn a Nuxt project using Nuxt UI, when a u-notification appears over a u-slideover, the notification is not clickable. The issue occurs because the u-slideover element blocks interactions with elements positioned above it. \n\nI have provided a reproduction link above where if you open the slideover, a notification appears after 1 sec and the notification is not interactive (action button does not work).\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3122,3123,3124],{"name":3035,"color":3036},{"name":3055,"color":3056},{"name":3058,"color":3056},3214,"Bug: u-notification Not Clickable When Positioned Over u-slideoveror or u-modal","2025-06-18T09:02:21Z","https://github.com/nuxt/ui/issues/3214",0.7266947,{"labels":3131,"number":3136,"owner":3025,"repository":3025,"state":3060,"title":3137,"updated_at":3138,"url":3139,"score":3140},[3132,3135],{"name":3133,"color":3134},"enhancement","8DEF37",{"name":3090,"color":3091},6068,"Modern build should detect browser compatibility","2023-01-22T15:50:56Z","https://github.com/nuxt/nuxt/issues/6068",0.727408,["Reactive",3142],{},["Set"],["ShallowReactive",3145],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fdiTbdXnmY_HkrIs8F93hhlG68F7I7Jhx9mX1ChMrPpU":-1},"/nuxt/ui/3462"]