\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```",[2069,2070,2071],{"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.72886,{"description":2078,"labels":2079,"number":2084,"owner":1994,"repository":1995,"state":2044,"title":2085,"updated_at":2086,"url":2087,"score":2088},"### Description\n\nStyles with tailwindcss 4.0.13 seem to be broken after updating from NuxtUI pervious alpha.\n\n```\n\"dependencies\": {\n \"@iconify-json/ri\": \"1.2.5\",\n \"@nuxt/ui\": \"3.0.0\",\n \"@vueuse/core\": \"12.7.0\",\n \"@vueuse/nuxt\": \"12.7.0\",\n }\n```\nmain.css\n```\n@import 'tailwindcss' theme(static);\n@import '@nuxt/ui';\n```\nHas anyone else ran into this issue and if so how did you fix it?",[2080,2083],{"name":2081,"color":2082},"question","d876e3",{"name":1988,"color":1989},3525,"Styles issue have upgrade from 3.0.0-alpha.13 to 3.0.0","2025-03-12T23:28:54Z","https://github.com/nuxt/ui/issues/3525",0.733367,{"description":2090,"labels":2091,"number":2097,"owner":1994,"repository":1994,"state":2044,"title":2098,"updated_at":2099,"url":2100,"score":2101},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.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: npm@9.4.2\r\n- Builder: -\r\n- User Config: devtools, pages\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt3-iframe-leak\n\n### Describe the bug\n\nIn my `index.vue` page I create an `iframe` element, which is rendering my `iframe.vue` page:\r\n\r\n```vue\r\n// index.vue\r\n\r\n\u003Ctemplate>\r\n \u003Cdiv>This is index page content!\u003C/div>\r\n \u003Ciframe src=\"/iframe\">\u003C/iframe>\r\n\u003C/template>\r\n```\r\n\r\n```vue\r\n// iframe.vue\r\n\r\n\u003Cscript setup>\r\n console.log('Hello World inside iframe!');\r\n\u003C/script>\r\n\r\n\u003Ctemplate>This is iframe content.\u003C/template>\r\n\r\n\u003Cstyle>\r\n* {\r\n color: red;\r\n}\r\n\u003C/style>\r\n```\r\n\r\nThe problem is that both style and script leak from iframe to parent page (`index.vue`).\r\nAll elements are red and I also see message in console log.\r\n\r\nHow to prevent iframe from applying styles and script to parent page?\r\n\r\nHere is a working [example][1] on Stackblitz.\r\n\r\n[![enter image description here][2]][2]\r\n\r\n\r\n [1]: https://stackblitz.com/edit/nuxt3-iframe-leak\r\n [2]: https://i.stack.imgur.com/CNH39.gif\n\n### Additional context\n\nI am trying to create an editor. Heavy work is done in worker and the rendered result I want to send to iframe and set content.\n\n### Logs\n\n_No response_",[2092,2095],{"name":2093,"color":2094},"3.x","29bc7f",{"name":2021,"color":2096},"E99695",24689,"IFrame style and script leak to parent page","2024-02-13T08:01:17Z","https://github.com/nuxt/nuxt/issues/24689",0.7353336,["Reactive",2103],{},["Set"],["ShallowReactive",2106],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"9rTLLR3sW_FazyxeLq5am6hJtl_o32Hjfjaoz_N1yX0":-1},"/nuxt/nuxt.com/1777"]