\n\n\u003C!-- Or more granular control -->\n\u003CMDC \n :value=\"content\"\n :ui=\"{\n prose: {\n h1: { leading: 'hidden', leadingIcon: 'hidden' },\n h2: { leading: 'hidden', leadingIcon: 'hidden' }\n }\n }\"\n/>\n```\n\n## Use Case\n\n**Displaying AI/LLM generated content** where anchor links are undesirable:\n- Game interfaces showing AI-generated text\n- Chat applications with LLM responses \n- Content previews or excerpts\n- Educational tools displaying sample outputs\n\nIn these scenarios, anchor links serve no purpose and can be distracting or break the user experience.\n\n## Expected Behavior\n\n- Component-level `:ui` prop should merge with global prose configuration\n- Should work consistently with both `@nuxt/content` and standalone MDC usage\n- Should not require global configuration changes for per-component customization\n\n## Current Versions\n\n- `@nuxt/ui-pro` (v3)\n- 'uiPro.mdc' set to true or false in `nuxt.config` does not make a difference\n\n## Additional Context\n\nThis would align with Nuxt UI's existing pattern of allowing component-level customization via `:ui` props, providing developers with fine-grained control while maintaining sensible defaults.\n\n### Additional context\n\n_No response_",[2865,2868,2871],{"name":2866,"color":2867},"enhancement","a2eeef",{"name":2869,"color":2870},"v3","49DCB8",{"name":2872,"color":2873},"triage","ffffff",4216,"nuxt","ui","open","Allow disabling anchor links per MDC component instance via :ui prop","2025-05-24T15:32:22Z","https://github.com/nuxt/ui/issues/4216",0.7691343,{"description":2883,"labels":2884,"number":2890,"owner":2875,"repository":2876,"state":2877,"title":2891,"updated_at":2892,"url":2893,"score":2894},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.9.0\n- Nuxt Version: 3.16.0\n- CLI Version: 3.22.5\n- Nitro Version: 2.11.6\n- Package Manager: pnpm@10.6.1\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.10\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/bold-cache-pkvmch\n\n### Description\n\nThe `InputMenu` component fails to handle nested properties (e.g., `'user.id'`, `'user.name'`) in `valueKey` and `labelKey` props, resulting in a TypeScript error.\n\n\n### Additional context\n\nProposed fix:\n\n```typescript\ntype NestedPathValue\u003CT, P extends string> = P extends `${infer Key}.${infer Rest}`\n ? Key extends keyof T\n ? NestedPathValue\u003CT[Key], Rest>\n : any\n : P extends keyof T\n ? T[P]\n : any;\n\nexport type SelectItemKey\u003CT> = T extends Record\u003Cstring, any>\n ? keyof T | (string & { [K in keyof T]?: NestedPathValue\u003CT, K & string> })\n : string;\n```\n\n### Logs\n\n```shell-script\n\n```",[2885,2888,2889],{"name":2886,"color":2887},"bug","d73a4a",{"name":2869,"color":2870},{"name":2872,"color":2873},3505,"TypeScript error with nested properties in `InputMenu` `valueKey` and `labelKey`","2025-03-09T12:13:54Z","https://github.com/nuxt/ui/issues/3505",0.77057207,{"description":2896,"labels":2897,"number":2904,"owner":2875,"repository":2875,"state":2877,"title":2905,"updated_at":2906,"url":2907,"score":2908},"As discussed in https://github.com/nuxt/ui/issues/159 this is a drain on people working on machine without 3d acceleration for css animations.\r\n\r\nCurrent solution implemented is to click on a hidden button on the top right corner *while* the animation is running. Obviously this is not the best solution as during that time the computer is extremely laggy so it's hard to move the mouse anyways on top of a css-animated background. \r\n\r\nAdditionally the button is hidden, so people have to go to github issues to find out.\r\n\r\nEither there should be FPS measurement to figure out if animations should be used, or please enable a `nuxt.config.js` option to disable this for the whole project.\r\n\r\nThank you!",[2898,2901],{"name":2899,"color":2900},"pending triage","E99695",{"name":2902,"color":2903},"ui-templates","bfd4f2",27083,"Add config option to disable build-time css animations and other fancy stuff","2024-06-30T11:09:24Z","https://github.com/nuxt/nuxt/issues/27083",0.77438223,{"description":2910,"labels":2911,"number":2915,"owner":2875,"repository":2876,"state":2877,"title":2916,"updated_at":2917,"url":2918,"score":2919},"### Description\n\nThis feature request proposes that the InputNumber component be enhanced with leading and trailing slot support. \n\nCurrently, components such as **Input**, **InputMenu**, **Select**, and **SelectMenu** already offer these slots for inserting custom content. For consistency across the UI library and to provide developers with a uniform customization experience, it is imperative that InputNumber is updated to include both leading and trailing slots. \n\n### Additional context\n\n_No response_",[2912,2913,2914],{"name":2866,"color":2867},{"name":2869,"color":2870},{"name":2872,"color":2873},4201,"[InputNumber] Add support for leading & trailing slots","2025-05-21T13:07:28Z","https://github.com/nuxt/ui/issues/4201",0.775008,{"description":2921,"labels":2922,"number":2926,"owner":2875,"repository":2876,"state":2927,"title":2928,"updated_at":2929,"url":2930,"score":2931},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.11.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.22.2\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.2.4\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, css\n- Runtime Modules: @nuxt/ui@3.0.0-beta.2\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.0-beta.2\n\n### Reproduction\n\nHere's a demo (https://codesandbox.io/p/devbox/nuxtui3-bug-3432-sphrpl)\n\n**index.vue**\n```\n\u003Ctemplate>\n \u003CUContainer>\n \u003CFooModal @some-action=\"fnHandleAction\" /> \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```",[2923,2924,2925],{"name":2886,"color":2887},{"name":2869,"color":2870},{"name":2872,"color":2873},3432,"closed","UModal and useOverlay compatibility Issue","2025-03-11T13:57:03Z","https://github.com/nuxt/ui/issues/3432",0.75624055,{"labels":2933,"number":2939,"owner":2875,"repository":2875,"state":2927,"title":2940,"updated_at":2941,"url":2942,"score":2943},[2934,2936],{"name":2866,"color":2935},"8DEF37",{"name":2937,"color":2938},"3.x","29bc7f",14505,"allow disabling auto imports","2024-04-16T07:56:52Z","https://github.com/nuxt/nuxt/issues/14505",0.75946057,{"labels":2945,"number":2950,"owner":2875,"repository":2875,"state":2927,"title":2951,"updated_at":2952,"url":2953,"score":2954},[2946,2947],{"name":2866,"color":2935},{"name":2948,"color":2949},"2.x","d4c5f9",5073,"Loading is prohibited on the pages","2023-01-22T15:50:48Z","https://github.com/nuxt/nuxt/issues/5073",0.76116276,{"labels":2956,"number":2959,"owner":2875,"repository":2875,"state":2927,"title":2960,"updated_at":2961,"url":2962,"score":2963},[2957,2958],{"name":2937,"color":2938},{"name":2899,"color":2900},14211,"Nuxt 3 ssr showing two components on page refresh?","2023-01-19T17:28:18Z","https://github.com/nuxt/nuxt/issues/14211",0.763256,{"labels":2965,"number":2968,"owner":2875,"repository":2875,"state":2927,"title":2969,"updated_at":2970,"url":2971,"score":2972},[2966,2967],{"name":2899,"color":2900},{"name":2948,"color":2949},7704,"Different updating behavior between modes","2023-01-22T15:36:04Z","https://github.com/nuxt/nuxt/issues/7704",0.763273,{"description":2974,"labels":2975,"number":2977,"owner":2875,"repository":2875,"state":2927,"title":2978,"updated_at":2979,"url":2980,"score":2981},"The forced vuex strict mode introduced in d9796be breaks part of my app. I understand that this was probably added to encourage best practices, but I think there should be an option to disable this behavior.\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1354\">#c1354\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2976],{"name":2948,"color":2949},1521,"disable vuex strict mode on dev","2023-01-18T15:41:52Z","https://github.com/nuxt/nuxt/issues/1521",0.7634873,["Reactive",2983],{},["Set"],["ShallowReactive",2986],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f0N2nFZdnOEKlMEiDQLLSwS_3ADvyvjh8zARMoZUlSLc":-1},"/nuxt/ui/3159"]