\n {{ selectedTheme }}\n \u003Cbr />\n\u003C/template>\n\n\u003Cscript setup lang=\"ts\">\n defineProps({\n media: {\n type: Object,\n required: true,\n },\n });\n\n const mediaPresets = useMediaPresets();\n\n const selectedTheme = ref('');\n\n const themeOptions = computed(() => {\n return mediaPresets.themes.map((theme) => ({\n id: theme.id,\n label: `${theme.emoji} ${theme.display}`,\n }));\n });\n\u003C/script>\n\n```\n\n\nWorking / Fix:\n```Vue\n\u003Ctemplate>\n \u003CUSelectMenu v-model=\"themesProxy\" name=\"labels\" :options=\"themeOptions\" searchable creatable placeholder=\"Select labels\" />\n {{ selectedTheme }}\n \u003Cbr />\n\u003C/template>\n\n\u003Cscript setup lang=\"ts\">\n defineProps({\n media: {\n type: Object,\n required: true,\n },\n });\n const mediaPresets = useMediaPresets();\n\n const selectedTheme = ref('my_value');\n\n const themeOptions = computed(() => {\n return mediaPresets.themes.map((theme) => ({ id: theme.id, label: `${theme.emoji} ${theme.display}` }));\n });\n\n const themesProxy = computed({\n get: () => {\n const existingTheme = themeOptions.value.find((theme) => theme.id === selectedTheme.value);\n if (existingTheme) return existingTheme;\n return { id: selectedTheme.value, label: selectedTheme.value?.replace(/\\s/g, '-')?.toLowerCase() };\n },\n\n set: (newValue: any) => {\n if (newValue.label && !newValue.id) newValue.id = newValue.label.replace(/\\s/g, '-').toLowerCase();\n selectedTheme.value = newValue.id;\n },\n });\n\n\u003C/script>\n\n```\n\n### Description\n\n\n\nWhen using the `creatable` option, the selected value does not show up properly in the input.\n\n\nThe v-model properly changes (`{{ selectedTheme }}` under the input), but it doesn't show up in the input afterward not in the \"create xyz' text \n\nThe issue seems to happens when not using `multiple`\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2945],{"name":2946,"color":2947},"bug","d73a4a",2342,"closed","[SelectMenu] `creatable` bugged when not using `multiple`","2024-11-12T17:11:21Z","https://github.com/nuxt/ui/issues/2342",0.7273084,{"description":2955,"labels":2956,"number":2958,"owner":2909,"repository":2928,"state":2949,"title":2959,"updated_at":2960,"url":2961,"score":2962},"### For what version of Nuxt UI are you suggesting this?\n\nv2.x\n\n### Description\n\nThe config of the divider component allows to define types:\n\n```\ntype: {\n solid: 'border-solid',\n dotted: 'border-dotted',\n dashed: 'border-dashed',\n},\n```\n\nHowever, the solid type is set by default and can only be changed per Divider component, not globally via config. It would be great to be able to set a custom default type like so:\n\n```\ndefault: {\n border: {\n type: 'dotted',\n },\n},\n```\n\n### Additional context\n\n_No response_",[2957],{"name":2922,"color":2923},2398,"Define default type for Divider","2024-10-19T12:19:23Z","https://github.com/nuxt/ui/issues/2398",0.7371054,{"description":2964,"labels":2965,"number":2970,"owner":2909,"repository":2909,"state":2949,"title":2971,"updated_at":2972,"url":2973,"score":2974},"### Describe the feature\r\n\r\nI hope this works in SSR mode.\r\ncurrently I have to wrap it in `\u003Cclient-only>`.\r\n\r\n```vue\r\n\u003Cteleport to=\"#test\">\r\n \u003Cdiv>test\u003C/div>\r\n\u003C/teleport>\r\n```\r\n\r\n### Additional information\r\n\r\n- [ ] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2966,2969],{"name":2967,"color":2968},"3.x","29bc7f",{"name":2903,"color":2904},21597,"teleport to specific element ","2023-06-20T09:46:04Z","https://github.com/nuxt/nuxt/issues/21597",0.7392179,{"description":2976,"labels":2977,"number":2978,"owner":2909,"repository":2979,"state":2949,"title":2980,"updated_at":2981,"url":2982,"score":2983},"### 📚 Description\r\n\r\nI got a 404 error when I accessed the **learn more** link on the [cloudflare](https://nuxt.com/deploy/cloudflare) page.\r\nI investigated the cause and found that the URL path was incorrect.",[],1520,"nuxt.com","bug: wrong link to Zero-Config Providers","2024-03-03T08:40:08Z","https://github.com/nuxt/nuxt.com/issues/1520",0.74055535,{"description":2985,"labels":2986,"number":2992,"owner":2909,"repository":2928,"state":2949,"title":2993,"updated_at":2994,"url":2995,"score":2996},"### 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```",[2987,2988,2989],{"name":2946,"color":2947},{"name":2925,"color":2926},{"name":2990,"color":2991},"triage","ffffff",3432,"UModal and useOverlay compatibility Issue","2025-03-11T13:57:03Z","https://github.com/nuxt/ui/issues/3432",0.74331945,{"description":2998,"labels":2999,"number":3002,"owner":2909,"repository":3003,"state":2949,"title":3004,"updated_at":3005,"url":3006,"score":3007},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v18.20.3\r\n- Nuxt Version: 3.13.2\r\n- CLI Version: 3.13.2\r\n- Nitro Version: 2.9.7\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: compatibilityDate, devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-fvrlkg?file=tests/app.test.ts,app.vue\r\n\r\ncancel the running process in the terminal and run `npm test` - you will see the failure.\n\n### Describe the bug\n\nIt seems that when `registerEndpoint` is called on a path containing two levels deep such as `/api/foo`, then subsequent calls to registerEndpoint on paths containing that root will fail to register. Ie, `registerEndpoint('/api/foo/bar', ...)` will silently fail. Calls to that deeper path when run in the test context receive the shorter path's response.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3000],{"name":2903,"color":3001},"5D08F5",956,"test-utils","registerEndpoint fails to register on deep paths","2024-11-26T16:14:09Z","https://github.com/nuxt/test-utils/issues/956",0.7503118,{"description":3009,"labels":3010,"number":3023,"owner":2909,"repository":2928,"state":2949,"title":3024,"updated_at":3025,"url":3026,"score":3027},"### Description\n\nIf I open one of these 3 (modal, sidebar, dropdown) nuxt ui is adding styles to the body which cause strange layout behaviors.\nI would like to costumize these or modify. Thats what currently gets added when opening a modal and causes problems\n```\n\u003Cbody style=\"padding-right: 9px; margin-right: 0px; --scrollbar-width: 9px; overflow: hidden; pointer-events: none;\">\n```\n\nIs there a way to do that right now?",[3011,3014,3015,3018,3021],{"name":3012,"color":3013},"question","d876e3",{"name":2925,"color":2926},{"name":3016,"color":3017},"reka-ui","56d799",{"name":3019,"color":3020},"closed-by-bot","ededed",{"name":3022,"color":3020},"stale",3078,"Scrolllock when opening modal, dropdown, sidebar","2025-06-18T09:02:37Z","https://github.com/nuxt/ui/issues/3078",0.7551337,["Reactive",3029],{},["Set"],["ShallowReactive",3032],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f8gjq297NPV_60Fmm3zowL_rhaAnns_H_Li0frR4mtIQ":-1},"/nuxt/ui/2287"]