",[2884,2887,2888],{"name":2885,"color":2886},"bug","d73a4a",{"name":2871,"color":2872},{"name":2889,"color":2890},"reka-ui","56d799",3947,"Unexpected drawer behavior when dragging content area (jumpy collapse & horizontal scroll flickering)","2025-06-05T10:38:05Z","https://github.com/nuxt/ui/issues/3947",0.7521639,{"description":2897,"labels":2898,"number":2904,"owner":2874,"repository":2875,"state":2876,"title":2905,"updated_at":2906,"url":2907,"score":2908},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: 3.17.4\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: pnpm@10.11.0\n- Builder: -\n- User Config: compatibilityDate, devtools, ssr, future, runtimeConfig, modules, css\n- Runtime Modules: @nuxt/eslint@1.3.1, @nuxt/image@1.10.0, @nuxt/ui@3.1.1, @pinia/nuxt@0.11.0\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/modest-shaw-dwjzc5\n\n### Description\n\n**What I'm trying to do:**\n\nI'm using the `UTooltip` component to show helpful text for buttons that only have icons (no text labels). These tooltips help users understand what each button does.\n\n**The issue:**\n\nI noticed that when a button with a tooltip is also used to open a `UModal`, the tooltip stops working after the modal is opened once. Specifically:\n\n- The tooltip works fine initially.\n- After I click the button (which has the tooltip) and the modal opens, the tooltip no longer appears when hovering over the button.\n- This only happens when the tooltip is on the same button that opens its own modal.\n\n**What I tried:**\n\n- Wrapping the button in `UTooltip`, both inside and outside the `UModal`, but the result is the same.\n- Setting `disableClosingTrigger` to `true` in the tooltip options\n- I added a second modal opened by another button without a tooltip, and that one does not break tooltips elsewhere. So the issue seems to be tied specifically to tooltips on buttons that open their own modal.",[2899,2900,2901],{"name":2885,"color":2886},{"name":2871,"color":2872},{"name":2902,"color":2903},"triage","ffffff",4274,"UTooltip breaks when attached to button that opens a UModal","2025-06-02T04:23:45Z","https://github.com/nuxt/ui/issues/4274",0.75937843,{"description":2910,"labels":2911,"number":2915,"owner":2874,"repository":2875,"state":2916,"title":2917,"updated_at":2918,"url":2919,"score":2920},"### 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```",[2912,2913,2914],{"name":2885,"color":2886},{"name":2871,"color":2872},{"name":2902,"color":2903},4135,"closed","Slideover blocks background interaction even with `overlay=false`","2025-05-13T12:59:56Z","https://github.com/nuxt/ui/issues/4135",0.6964856,{"description":2922,"labels":2923,"number":2928,"owner":2874,"repository":2875,"state":2916,"title":2929,"updated_at":2930,"url":2931,"score":2932},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.x\n\n### Description\n\nAFAIK there is currently no documented way to prevent the popover from opening automatically through click or hover.\n\nExample API:\n\n```\n\u003CUPopover mode=\"manual\">\n \u003CUButton>I don't do anything\u003C/UButton\n\u003C/UPopover>\n```\n\n### Additional context\n\nRelated to #721 (but not fixed)",[2924,2927],{"name":2925,"color":2926},"enhancement","a2eeef",{"name":2871,"color":2872},2925,"Popover manual mode with no click nor hover","2025-05-10T17:19:51Z","https://github.com/nuxt/ui/issues/2925",0.718824,{"description":2934,"labels":2935,"number":2944,"owner":2874,"repository":2874,"state":2916,"title":2945,"updated_at":2946,"url":2947,"score":2948},"### Version\n\n[v2.2.0](https://github.com/nuxt.js/releases/tag/v2.2.0)\n\n### Reproduction link\n\n[https://codesandbox.io/s/vm3okyjyol](https://codesandbox.io/s/vm3okyjyol)\n\nAdditional reproduction and debugging examples provided by manniL (small edits by me):\n\nhttps://codesandbox.io/s/5zwmmxqzvl (nuxt 2.2.0)\nhttps://codesandbox.io/s/k02x548j45 (nuxt 1.4.4 - same code as above, but BUG NOT OCCURRING HERE)\n\n### Steps to reproduce\n\nClick \"Go to TEST page\"\nClick \"Click here to open the nuxt child!\"\nClick outside the grey box to close the nuxt child\nClick \"Click here to open the nuxt child!\" again\n\n### What is expected ?\n\nAfter the second click on \"Click here to open the nuxt child!\" on the TEST page, the gray box (=nuxt-child) should stay visible\n\n### What is actually happening?\n\nInstead the child disappears almost immediately, which means the click to navigate to the child page is the same click that closes the child page\n\n### Additional comments?\n\nThe grey box is a nuxt-child. When clicking outside the child, the child is closed. This is done via a v-click-outside directive. Note that the same code worked fine and as expected in 1.4.4 and earlier.\n\nOn the main /index.vue page everything works correct. The issue occurs on all pages except for the main /index.vue page. If I were to create /test/index.vue, and a nuxt-child /test/index/subpage.vue, the bug would occur as well.\n\nThe issue only occurs from the second opening of the nuxt-child on. The first time everything works as expected. My assumption is that the nuxt-child somehow stays active/ready. Check the logs to see that when the issue occurs, the nuxt-child is mounted and then the same click that opened the nuxt-child triggers a click-event through the nuxt-child's click-outside directive.\n\n\n\n\u003C!--cmty-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c8115\">#c8115\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2936,2938,2941],{"name":2937,"color":2903},"stale",{"name":2939,"color":2940},"pending triage","E99695",{"name":2942,"color":2943},"2.x","d4c5f9",4306,"Nuxt-child sometimes mounted before click event that opens it","2023-01-22T15:30:07Z","https://github.com/nuxt/nuxt/issues/4306",0.7269345,{"labels":2950,"number":2953,"owner":2874,"repository":2874,"state":2916,"title":2954,"updated_at":2955,"url":2956,"score":2957},[2951,2952],{"name":2939,"color":2940},{"name":2942,"color":2943},5456,"Slide-enter animations are broken although slide-leave are working well","2023-01-22T15:33:04Z","https://github.com/nuxt/nuxt/issues/5456",0.73153937,{"description":2959,"labels":2960,"number":2963,"owner":2874,"repository":2875,"state":2916,"title":2964,"updated_at":2965,"url":2966,"score":2967},"### Environment\n\n- Operating System: Darwin\n- Node Version: v18.20.6\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: yarn@1.22.22\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.13\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/modest-agnesi-drlrh4?file=%2Fapp%2Fpages%2Findex.vue%3A24%2C24\n\n### Description\n\nWhen I close a `UDrawer` that I opened via an action from a `UDropdownMenu`, the style on my \u003Cbody> tag still contains `overflow: hidden` and `user-select: none`, which prevents interaction with the page.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2961,2962],{"name":2885,"color":2886},{"name":2871,"color":2872},3406,"User interaction lock after a Drawer/DropdownMenu","2025-02-27T20:57:27Z","https://github.com/nuxt/ui/issues/3406",0.73269045,{"labels":2969,"number":2972,"owner":2874,"repository":2874,"state":2916,"title":2973,"updated_at":2974,"url":2975,"score":2976},[2970,2971],{"name":2939,"color":2940},{"name":2942,"color":2943},10593,"@click listener on \u003Cnuxt-link> or \u003Crouter-link> no longer works inside page components on Vue 2.7","2023-02-08T19:37:35Z","https://github.com/nuxt/nuxt/issues/10593",0.7384532,{"description":2978,"labels":2979,"number":2982,"owner":2874,"repository":2983,"state":2916,"title":2984,"updated_at":2985,"url":2986,"score":2987},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v18.18.0`\r\n- Nuxt Version: `3.9.0`\r\n- CLI Version: `3.10.0`\r\n- Nitro Version: `2.8.1`\r\n- Package Manager: `bun@1.0.20`\r\n- Builder: `-`\r\n- User Config: `devtools`, `modules`, `primevue`, `css`, `components`, `imports`, `i18n`, `supabase`, `runtimeConfig`, `experimental`, `vite`, `testUtils`\r\n- Runtime Modules: `@vueuse/nuxt@10.7.1`, `@nuxtjs/supabase@1.1.4`, `@nuxtjs/eslint-module@4.1.0`, `@nuxtjs/i18n@8.0.0-rc.5`, `@nuxtjs/stylelint-module@5.1.0`, `@pinia/nuxt@0.5.1`, `@pinia-plugin-persistedstate/nuxt@1.2.0`, `@element-plus/nuxt@1.0.7`, `nuxt-icon@0.6.8`, `@samk-dev/nuxt-vcalendar@1.0.2`, `@nuxt/image@1.1.0`, `nuxt-primevue@0.2.2`, `dayjs-nuxt@2.1.9`, `@nuxt/test-utils/module@3.9.0`\r\n- Build Modules: `-`\r\n\r\n\r\n### Reproduction\r\n\r\nupdate the package to 3.9.0. and put '@nuxt/test-utils/module' into modules in nuxt.config.\r\nthen in some reasons, it goes error when nuxt modules trying to import explicitly from #imports or #build.\r\n\r\n### Describe the bug\r\n\r\nI just updated test-utils as nuxt-vitest archived, and set config like you mentioned.\r\nand running nuxt, it goes error.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n```shell-script\r\nCould not resolve \"#imports\"\r\n\r\n node_modules/@nuxt/test-utils/dist/runtime-utils/index.mjs:5:46:\r\n 5 │ import { defineComponent, useRouter, h } from '#imports';\r\n ╵ ~~~~~~~~~~\r\n\r\n You can mark the path \"#imports\" as external to exclude it from the bundle, which will remove this\r\n error and leave the unresolved path in the bundle.\r\n\r\n✘ [ERROR] Could not resolve \"#build/root-component.mjs\"\r\n\r\n node_modules/@nuxt/test-utils/dist/runtime-utils/index.mjs:6:21:\r\n 6 │ import NuxtRoot from '#build/root-component.mjs';\r\n ╵ ~~~~~~~~~~~~~~~~~~~~~~~~~~~\r\n\r\n You can mark the path \"#build/root-component.mjs\" as external to exclude it from the bundle, which\r\n will remove this error and leave the unresolved path in the bundle.\r\n-------------------------------------------\r\nerror while updating dependencies: 2:11:00 PM\r\nError: Build failed with 2 errors:\r\nnode_modules/@nuxt/test-utils/dist/runtime-utils/index.mjs:5:46: ERROR: Could not resolve \"#imports\"\r\nnode_modules/@nuxt/test-utils/dist/runtime-utils/index.mjs:6:21: ERROR: Could not resolve \"#build/root-component.mjs\"\r\n```\r\n",[2980],{"name":2939,"color":2981},"5D08F5",681,"test-utils","Error occurred after updating 3.9","2024-08-02T12:51:47Z","https://github.com/nuxt/test-utils/issues/681",0.73955435,["Reactive",2989],{},["Set"],["ShallowReactive",2992],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fteVe6o66oo3pVZMw5e5DhtkcNhgh9iekHooN-NrsShg":-1},"/nuxt/ui/4289"]