\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```",[2918,2919,2920],{"name":2894,"color":2895},{"name":2871,"color":2872},{"name":2898,"color":2899},3432,"UModal and useOverlay compatibility Issue","2025-03-11T13:57:03Z","https://github.com/nuxt/ui/issues/3432",0.6883303,{"description":2927,"labels":2928,"number":2931,"owner":2874,"repository":2875,"state":2910,"title":2932,"updated_at":2933,"url":2934,"score":2935},"### Environment\n\n- Operating System: Linux\n- Node Version: v23.3.0\n- Nuxt Version: 3.15.1\n- CLI Version: 3.18.2\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.13.2\n- Builder: -\n- User Config: devtools, modules, css, future, compatibilityDate\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.9, @nuxt/eslint@0.7.4\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.15.1\n\n### Reproduction\n\nhttps://github.com/fl5brkv/nuxt-issue\n\n### Description\n\nI installed nuxt ui 3 from the official nuxt ui starter, just wanted to try the calendar, but it doesnt work. Throwing me warnings in console.log.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n[Vue warn]: Failed to resolve component: UCalendar\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement. \n at \u003CIndex onVnodeUnmounted=fn\u003ConVnodeUnmounted> ref=Ref\u003C undefined > > \n at \u003CAnonymous key=\"/\" vnode= Object route= Object ... > \n at \u003CRouterView name=undefined route=undefined > \n at \u003CNuxtPage > \n at \u003CToastProvider swipe-direction=\"right\" duration=5000 > \n at \u003CToaster key=0 > \n at \u003CTooltipProvider > \n at \u003CConfigProvider use-id=fn\u003Cuse-id> dir=\"ltr\" > \n at \u003CApp > \n at \u003CApp key=4 > \n at \u003CNuxtRoot>\n\nruntime-core.esm-bundler.js?v=b66559bc:50 [Vue warn]: Hydration node mismatch:\n- rendered on server: \u003C!----> \n- expected on client: UCalendar \n at \u003CIndex onVnodeUnmounted=fn\u003ConVnodeUnmounted> ref=Ref\u003C undefined > > \n at \u003CAnonymous key=\"/\" vnode= Object route= Object ... > \n at \u003CRouterView name=undefined route=undefined > \n at \u003CNuxtPage > \n at \u003CToastProvider swipe-direction=\"right\" duration=5000 > \n at \u003CToaster key=0 > \n at \u003CTooltipProvider > \n at \u003CConfigProvider use-id=fn\u003Cuse-id> dir=\"ltr\" > \n at \u003CApp > \n at \u003CApp key=4 > \n at \u003CNuxtRoot>\n```",[2929,2930],{"name":2894,"color":2895},{"name":2871,"color":2872},3044,"\u003CUCalendar /> isn't rendering","2025-01-08T09:24:13Z","https://github.com/nuxt/ui/issues/3044",0.6914916,{"description":2937,"labels":2938,"number":2941,"owner":2874,"repository":2875,"state":2910,"title":2942,"updated_at":2943,"url":2944,"score":2945},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v20.16.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.22.1\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.8.1\n- Builder: -\n- User Config: devtools, compatibilityDate, modules, app, css, colorMode, svgSprite, future, imports, runtimeConfig, ssr\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.13, @nuxt/eslint@1.1.0, @nuxt/icon@1.10.3, @nuxtjs/svg-sprite@1.0.2, @nuxt/image@1.9.0, @vueuse/nuxt@12.7.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.0-alpha.13\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/stupefied-roentgen-y6tdsd\n\n### Description\n\n### Help Nuxt ui 3 table not reactive\n\nWhen I click the button, the table doesn't update. However, when I print the array object, the data is added, but the table still does not update\n\nhttps://codesandbox.io/p/devbox/stupefied-roentgen-y6tdsd\n\nThank you for help\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2939,2940],{"name":2894,"color":2895},{"name":2871,"color":2872},3377,"UI Table is not reactive","2025-02-27T21:19:42Z","https://github.com/nuxt/ui/issues/3377",0.6965156,{"description":2947,"labels":2948,"number":2953,"owner":2874,"repository":2875,"state":2910,"title":2954,"updated_at":2955,"url":2956,"score":2957},"### Description\n\nIt's shorter and can save traffic.\n\n### Additional context\n\n_No response_",[2949,2952],{"name":2950,"color":2951},"enhancement","a2eeef",{"name":2871,"color":2872},3250,"Use `foo-(--bar)` instead of `foo-[var(--bar)]` for tailwindcss classes","2025-02-07T10:24:17Z","https://github.com/nuxt/ui/issues/3250",0.69696325,{"description":2959,"labels":2960,"number":2966,"owner":2874,"repository":2875,"state":2910,"title":2967,"updated_at":2968,"url":2969,"score":2970},"### Reproduction\n\nhttps://ui3.nuxt.dev/components/select-menu#search-input\n\n### Description\n\nAccording to the docs `resetSearchTermOnBlur` is set to true by default but the search input never resets as you can see in the example from the docs. Even when explicitly setting `:reset-search-term-on-blur=\"true\"` it never resets.\n",[2961,2962,2963],{"name":2894,"color":2895},{"name":2871,"color":2872},{"name":2964,"color":2965},"reka-ui","56d799",2912,"v3: SelectMenu search input never resets","2025-01-13T10:26:18Z","https://github.com/nuxt/ui/issues/2912",0.6981221,{"description":2972,"labels":2973,"number":2979,"owner":2874,"repository":2875,"state":2910,"title":2980,"updated_at":2981,"url":2982,"score":2983},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.18.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.16.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.12.3\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/image@1.8.1, @nuxt/content@2.13.4, @nuxthq/studio@1.1.2, @nuxt/ui-pro@3.0.0-alpha.10, @nuxtjs/plausible@1.2.0, @nuxtjs/seo@2.0.2, @vueuse/nuxt@12.0.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0.alpha10\n\n### Reproduction\n\nhttps://ui3.nuxt.dev/components/button#loading (example with `loading-auto`)\n\n### Description\n\nWhen using a `UIButton` component with an `@click` event, the cursor does not change to `cursor-pointer`, which may confuse users about the button's clickability.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2974,2975,2978],{"name":2894,"color":2895},{"name":2976,"color":2977},"duplicate","cfd3d7",{"name":2871,"color":2872},2940,"`cursor-pointer` is missing on `UButton` with an `@click` event","2025-04-02T09:37:12Z","https://github.com/nuxt/ui/issues/2940",0.7005984,["Reactive",2985],{},["Set"],["ShallowReactive",2988],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fFLytn0xS0NXXHIZK5MS4KTfUMDCqri_EHEK2p5MAh0I":-1},"/nuxt/ui/2931"]