\u003Cbr />\n \u003CUButton @click=\"fnOpenModal\">Open FooModal from code\u003C/UButton>\n \u003C/UContainer>\n\u003C/template>\n\n\u003Cscript lang=\"ts\" setup>\n import { FooModal } from '#components';\n\n const overlay = useOverlay();\n\n const foo = overlay.create(FooModal);\n\n const fnOpenModal = async () => {\n foo.open();\n };\n\n const fnHandleAction = (action) => {\n console.log(\"Handle FooModal action: \", action);\n };\n\u003C/script>\n```\n\n**FooModal**\n```\n\u003Ctemplate>\n \u003CUModal v-model:open=\"open\" title=\"Foobar\">\n \u003CUButton label=\"Open FooModal from modal\" color=\"neutral\" variant=\"subtle\" />\n\n \u003Ctemplate #body>\n \u003CUButton @click=\"click()\" >Submit\u003C/UButton>\n \u003C/template>\n \u003C/UModal>\n\u003C/template>\n\n\u003Cscript lang=\"ts\" setup>\n const open = ref(false);\n\n const emits = defineEmits(['some-action']);\n\n const click = () => {\n console.log(\"clicked from inside the modal\");\n emits('some-action', 'closing'); //emits does not work if Modal opened using useOverlay.\n open.value = false; //closing modal does not work if Modal opened using useOverlay.\n };\n\u003C/script>\n```\n\n### Description\n\nHello Nuxt UI team,\n\nThank you for providing a high-quality UI library. I truly appreciate the effort you put into creating and maintaining it.\n\nI have encountered an issue while using `UModal` in my application. The modal is used to create and/or update database entries, and it needs to be opened in two different ways:\n\n1. Via a `UButton` that is always present on the screen (provided by the modal itself).\n2. Programmatically, through a link in a dropdown menu, using `useOverlay`.\n\nWhen the modal is opened using the first method, everything works as expected. However, when it is opened programmatically using the second method, the modal does not behave the same way. Specifically:\n\n- I am unable to trigger an `emit` to notify the parent component that the update was successful.\n- The modal does not close properly using the `open.value = false` technique.\n\nI am unsure if this behavior is intentional or a bug. I was under the impression that `UModal` and `useOverlay` should work seamlessly together and exhibit consistent behavior. Could you please confirm whether this is a valid concern?\n\nThank you for your time and attention to this matter. I look forward to your guidance.\n\n**Note**: You'll also notice that the button within the modal appears on the screen when opened using `useOverlay`. It would be helpful if it could be hidden automatically, but I believe this is something I can control easily. As such, I do not consider this to be a bug.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3205,3206,3207],{"name":3173,"color":3174},{"name":3176,"color":3177},{"name":3208,"color":3209},"triage","ffffff",3432,"UModal and useOverlay compatibility Issue","2025-03-11T13:57:03Z","https://github.com/nuxt/ui/issues/3432",0.7100932,{"description":3216,"labels":3217,"number":3220,"owner":3149,"repository":3163,"state":3164,"title":3221,"updated_at":3222,"url":3223,"score":3224},"### Description\n\nRight now there is no aria-* attributes in form inputs, that should be required to meet wcag aa:\n- associate form label elements with controls: id on the input and label-for in the label referencing the input id\n- aria-describedby for messages and errors on each form input\n- aria-invalid=\"true\" on each invalid form input (plus the aria-describedby referencing the error)\n- include form error recovery: via `Error alert, then focus`, `Errors on top` or `Inline errors`: I always use `Errors on top` + `Inline errors` (ui using inline errors)\n\nFor reference: https://webaim.org/techniques/formvalidation/\n\n\n### Additional context\n\n_No response_",[3218,3219],{"name":3187,"color":3188},{"name":3176,"color":3177},3111,"add a11y to form stuff","2025-01-25T13:14:07Z","https://github.com/nuxt/ui/issues/3111",0.7117832,{"description":3226,"labels":3227,"number":3228,"owner":3149,"repository":3150,"state":3164,"title":3229,"updated_at":3230,"url":3231,"score":3232},"Clicking the button close the dialog but nothing happens. Either on chrome or firefox.\n\nCome from https://github.com/nuxt/nuxt/issues/30827\n",[],1777,"Ask AI doesn't work for me","2025-02-05T10:21:53Z","https://github.com/nuxt/nuxt.com/issues/1777",0.7187702,{"description":3234,"labels":3235,"number":3239,"owner":3149,"repository":3240,"state":3164,"title":3241,"updated_at":3242,"url":3243,"score":3244},"### 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",[3236],{"name":3237,"color":3238},"pending triage","5D08F5",681,"test-utils","Error occurred after updating 3.9","2024-08-02T12:51:47Z","https://github.com/nuxt/test-utils/issues/681",0.7223632,{"description":3246,"labels":3247,"number":3259,"owner":3149,"repository":3163,"state":3164,"title":3260,"updated_at":3261,"url":3262,"score":3263},"### Environment\n\nOperating System: Windows 11\nNode Version: v22.14.0\nNuxt Version: 3.17.4\nNitro Version: 2.11.12\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.3\n\n### Description\n\nHi,\nWhen I use the mouseenter and mouseleave or mouseover and mouseout events, the following error appears and the events don't work:\n\n\"[Vue warn]: Extraneous non-emits event listeners (mouseenter, mouseleave) were passed to component but could not be automatically inherited because component renders fragment or text root nodes. If the listener is intended to be a component custom event listener only, declare it using the emits option.\"\n\nWhat should I do? Can you help me?\n",[3248,3249,3252,3253,3256],{"name":3173,"color":3174},{"name":3250,"color":3251},"needs reproduction","CB47CF",{"name":3176,"color":3177},{"name":3254,"color":3255},"nuxt/ui-pro","00dc82",{"name":3257,"color":3258},"closed-by-bot","ededed",4268,"Extraneous non-emits event listeners (mouseenter, mouseleave) on UDashboardSidebar component","2025-08-15T02:16:25Z","https://github.com/nuxt/ui/issues/4268",0.7227277,["Reactive",3265],{},["Set"],["ShallowReactive",3268],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fhIiweh3wUPyWK-uLBgY03jLONMtsTnMbtIso5lcmbyo":-1},"/nuxt/test-utils/451"]