\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```",[2058,2059,2060],{"name":2005,"color":2006},{"name":1988,"color":1989},{"name":1991,"color":1992},3432,"UModal and useOverlay compatibility Issue","2025-03-11T13:57:03Z","https://github.com/nuxt/ui/issues/3432",0.7408585,{"description":2067,"labels":2068,"number":2072,"owner":1994,"repository":1994,"state":2022,"title":2073,"updated_at":2074,"url":2075,"score":2076},"### Environment\n\n- Operating System: Windows_NT\r\n- Node Version: v18.20.3\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: npm@10.8.1\r\n- Builder: -\r\n- User Config: srcDir, components, devtools, modules, vite, hooks, app, runtimeConfig\r\n- Runtime Modules: @vueuse/nuxt@10.11.0\r\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-vxspid?file=src%2Fplugins%2FclickOutside.ts\n\n### Describe the bug\n\nHello, not sure if you can help with this. I'm trying to implement a basic click outside functionality in a nuxt app.\r\nI'm trying to use @vueuse/components and I import @vueuse/nuxt in modules in nuxt config.\r\nmodules: [\r\n '@vueuse/nuxt',\r\n ],\r\n Then I create a plugin with this\r\n \r\n import { vOnClickOutside } from '@vueuse/components'\r\n\r\nexport default defineNuxtPlugin((nuxtApp) => {\r\n nuxtApp.vueApp.directive('clickOutside', vOnClickOutside)\r\n})\r\n\r\nHowever, I keep receiving this message after trying to use the dom element \u003COnClickOutside> in the HTML of the page :\r\n\r\n[Vue warn]: Failed to resolve component: OnClickOutside \r\nIf this is a native custom element, make sure to exclude it from \r\ncomponent resolution via compilerOptions.isCustomElement.\r\n\r\nIf I try to use the v-on-click-outside directive in the HTML I receive the following error : \r\n\r\n[Vue warn]: Failed to resolve directive: on-click-outside\r\n\r\nI don't know which would be a correct solution for this.\r\n\r\nThank you in advance for your help\r\n\r\nCarlota\r\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2069],{"name":2070,"color":2071},"pending triage","E99695",28060,"@vueuse/nuxt + @vueuse/components => vOnClickOutside","2024-07-05T22:04:25Z","https://github.com/nuxt/nuxt/issues/28060",0.7421956,{"description":2078,"labels":2079,"number":2081,"owner":1994,"repository":1994,"state":2022,"title":2082,"updated_at":2083,"url":2084,"score":2085},"Use android 6.0 build-in Browser, run examples/vuex-store-modules\r\n\r\nThe button in example can NOT be clicked\r\n\r\nThe browser output a error:\r\n\r\n> 09-07 08:30:25.107 2912 2912 E browser : Console: Uncaught TypeError: filenames.find is not a function http://192.168.0.102:3000/_nuxt/nuxt.bundle.6090fac5842dbbea9c6a.js:1774\r\n\r\n\r\nFull output:\r\n>09-07 08:30:25.107 2912 2912 E browser : Console: Uncaught TypeError: filenames.find is not a function http://192.168.0.102:3000/_nuxt/nuxt.bundle.6090fac5842dbbea9c6a.js:1774\r\n09-07 08:30:25.148 2912 2912 I browser : Console: Download the Vue Devtools extension for a better development experience:\r\n09-07 08:30:25.148 2912 2912 I browser : https://github.com/vuejs/vue-devtools http://192.168.0.102:3000/_nuxt/vendor.bundle.601df7a36ddb46c8dab5.js:7122\r\n09-07 08:30:25.149 2912 2912 I browser : Console: You are running Vue in development mode.\r\n09-07 08:30:25.149 2912 2912 I browser : Make sure to turn on production mode when deploying for production.\r\n09-07 08:30:25.149 2912 2912 I browser : See more tips at https://vuejs.org/guide/deployment.html http://192.168.0.102:3000/_nuxt/vendor.bundle.601df7a36ddb46c8dab5.js:7132\r\n09-07 08:30:25.230 2912 2912 I browser : Console: [HMR] connected http://192.168.0.102:3000/_nuxt/vendor.bundle.601df7a36ddb46c8dab5.js:13240\r\nwuyongzhideMacBook-Pro:platform-tools wuyongzhi$\r\n\r\n\r\ni testing it on real phone and emulator, both has issue.\r\n\r\nbut, i run examples/vuex-store has NOT issue. \n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1430\">#c1430\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2080],{"name":2048,"color":2049},1599,"Browser compatibility on Android 6.0 build-in browser","2023-01-18T15:42:00Z","https://github.com/nuxt/nuxt/issues/1599",0.74306804,{"labels":2087,"number":2089,"owner":1994,"repository":1994,"state":2022,"title":2051,"updated_at":2090,"url":2091,"score":2092},[2088],{"name":2048,"color":2049},6214,"2023-01-18T20:44:02Z","https://github.com/nuxt/nuxt/issues/6214",0.7474704,["Reactive",2094],{},["Set"],["ShallowReactive",2097],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"pmN2FGyUE10xzX-J1oj6ibo5wZ3hwFhWzG3wiZnfnmU":-1},"/nuxt/nuxt.com/1245"]