\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```",[2908,2909,2910],{"name":2897,"color":2898},{"name":2871,"color":2872},{"name":2911,"color":2912},"triage","ffffff",3432,"UModal and useOverlay compatibility Issue","2025-03-11T13:57:03Z","https://github.com/nuxt/ui/issues/3432",0.6616371,{"description":2919,"labels":2920,"number":2923,"owner":2874,"repository":2875,"state":2900,"title":2924,"updated_at":2925,"url":2926,"score":2927},"### Description\n\nI want to configure my Nuxt UI v3 project only to use black and white colors with the neutral palette from Tailwind, similar to the one found in shadcn. I understand Nuxt UI supports Tailwind CSS theming, but I’m unsure of the best/recommended way to override all component colors globally",[2921,2922],{"name":2868,"color":2869},{"name":2871,"color":2872},3200,"How to create a black & white only theme in Nuxt UI v3","2025-02-09T12:59:38Z","https://github.com/nuxt/ui/issues/3200",0.67859834,{"description":2929,"labels":2930,"number":2931,"owner":2874,"repository":2932,"state":2900,"title":2933,"updated_at":2934,"url":2935,"score":2936},"If you go to any blog and click `Edit on Github` on aside it will bring you to a 404 on github.\r\n\r\nCode that is incorrect: https://github.com/nuxt/nuxt.com/blob/a9b1e32c93714f23703f12add0f0c17cc518bd2a/pages/blog/%5Bslug%5D.vue#L66\r\n\r\nNeeds to be: \r\n\r\n```\r\nhttps://github.com/nuxt/nuxt.com/edit/main/content/${article.value._file}\r\n```",[],1533,"nuxt.com","blog \"Edit on Github\" url is broke.","2024-03-11T22:23:34Z","https://github.com/nuxt/nuxt.com/issues/1533",0.6804153,{"description":2938,"labels":2939,"number":2944,"owner":2874,"repository":2875,"state":2900,"title":2945,"updated_at":2946,"url":2947,"score":2948},"### 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_",[2940,2943],{"name":2941,"color":2942},"enhancement","a2eeef",{"name":2871,"color":2872},3111,"add a11y to form stuff","2025-01-25T13:14:07Z","https://github.com/nuxt/ui/issues/3111",0.6811099,{"description":2950,"labels":2951,"number":2954,"owner":2874,"repository":2875,"state":2900,"title":2955,"updated_at":2956,"url":2957,"score":2958},"### Description\n\nIt's shorter and can save traffic.\n\n### Additional context\n\n_No response_",[2952,2953],{"name":2941,"color":2942},{"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.68295217,{"description":2960,"labels":2961,"number":2964,"owner":2874,"repository":2932,"state":2900,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### Environment\n\nMacOS, Chrome, Firefox and Safari\n\n### Reproduction\n\n### to reproduce\n1.go to the a module category page with direct access, such as [security](https://nuxt.com/modules?category=Security) or [devtools](https://nuxt.com/modules?category=Devtools) or do a page refresh from any of the category page.\n2. open a bunch of module links in a NEW TAB via right click \"open in a new tab\" or CMD + Click\n3. find out that when you open a new link to a module, for instance, [nuxt-security](), the target URL that is actually opened is [nuxt-image](https://nuxt.com/modules/image)\n\n\nIt happens when opening a new tabs from the \"security\" category `?category=Security`\nIt only happens when opening the security category on direct access by typing accessing url directly\nIt does not happen when opening the link on the same window on the `?category=Security` page\nIt does not happen when opening links from [module page without category slug](https://nuxt.com/modules)\n\n\n\n### Describe the bug\n\nThere is a unpredictable behaviour. When i click on nuxt modules cards that links to Nuxt 3 modules on a new tab, it open a different link than the expected one.\n\nWhen I try direct access by clicking on the link (not a open in a new tab or CMD + Click , it works as expected\n\n### Additional context\n\n\n### additional info\nreproduced on Chrome and Safari.\nhttps://github.com/user-attachments/assets/0742a7fa-80c6-4556-b31c-26f181d9f92b\n\n### guess\n when browsing a category with an active filter, the opened links pattern (`@nuxtjs/kinde`, `@logto/nuxt`, `@nuxt/devtools `) actually match the links displayed on the [root main modules page](https://nuxt.com/modules) without active filter `https://nuxt.com/modules`.\n\n### Logs\n\n```shell-script\n\n```",[2962],{"name":2897,"color":2963},"ff281a",1750,"(nuxt website): module cards links are inconsistent at open new tab","2025-03-21T16:12:36Z","https://github.com/nuxt/nuxt.com/issues/1750",0.68372303,{"description":2970,"labels":2971,"number":2974,"owner":2874,"repository":2875,"state":2900,"title":2975,"updated_at":2976,"url":2977,"score":2978},"### Description\n\ni noticed that NUXT UI / NUXT UI PRO were refactored to use tailwind's new version 3 stuff + radix...\n\ni just went to the tailwind docs today and it looks like they just skipped right past their new version 3 and went to version 4...\n\nany ideas how this effects NUXT UI/PRO? \n\nMy undersanding is that version 3->4 means it was a semver breaking change?",[2972,2973],{"name":2868,"color":2869},{"name":2871,"color":2872},3167,"tailwind version 4..?","2025-01-24T10:17:32Z","https://github.com/nuxt/ui/issues/3167",0.68463737,["Reactive",2980],{},["Set"],["ShallowReactive",2983],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f8wtkh_gKGq59NC9ELfiSb57LE0t7WzhZP86X5w-ruTw":-1},"/nuxt/ui/2569"]