\n\u003C/template>\n```\n\nI think created items should emit `change` so we can validate them properly.\n\nAdditionally, because of https://github.com/nuxt/ui/issues/3736,the field always starts in an error state when a new item is created in certain conditions (regardless of whether the item meets the schema's requirements or not).\n\n------\n\nCurrent workaround is to run the validation manaully on a field after mutating the model:\n\n```ts\nasync function onCreate(item: string) {\n selected.value = item\n\n await formRef.value?.validate({ name: 'fieldName' })\n}\n```",[3180,3183],{"name":3181,"color":3182},"enhancement","a2eeef",{"name":3184,"color":3185},"v3","49DCB8",4139,"nuxt","ui","open","USelectMenu should emit 'change' after creating an item","2025-05-13T09:15:02Z","https://github.com/nuxt/ui/issues/4139",0.7608368,{"description":3195,"labels":3196,"number":3203,"owner":3187,"repository":3187,"state":3204,"title":3205,"updated_at":3206,"url":3207,"score":3208},"### Describe the feature\n\nThe event emitter & listener should be a built-in feature because it's so important. Yes we can use a third party plugin like https://www.npmjs.com/package/mitt, but isn't it great that nuxt/vue 3 has this feature by default like nuxt/vue 2?\n\n### Additional information\n\n- [ ] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3197,3200],{"name":3198,"color":3199},"3.x","29bc7f",{"name":3201,"color":3202},"pending triage","E99695",19629,"closed","Event emitter & listener","2023-03-13T06:59:40Z","https://github.com/nuxt/nuxt/issues/19629",0.70639837,{"description":3210,"labels":3211,"number":3219,"owner":3187,"repository":3188,"state":3204,"title":3220,"updated_at":3221,"url":3222,"score":3223},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v22.16.0\n- Nuxt Version: 3.17.6\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.13\n- Package Manager: pnpm@10.12.4\n- Builder: -\n- User Config: -\n- Runtime Modules: @nuxt/ui@3.2.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.2.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/serene-river-hypccq\n\n### Description\n\nupdating to 3.2.0, the cancel button does not display\n\n```ts\nconst overlay = useOverlay()\nconst dialog = overlay.create(VDialog, {\n props: {\n showCancelButton: true,\n },\n})\n\nfunction showDialog() {\n dialog.open({\n title: 'Lorem Ipsum',\n description: 'Lorem ipsum dolor sit amet, consectetur adipiscing elit.',\n })\n}\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3212,3215,3216],{"name":3213,"color":3214},"bug","d73a4a",{"name":3184,"color":3185},{"name":3217,"color":3218},"triage","ffffff",4468,"useOverlay: passing props to open will override the props of the create","2025-07-08T08:51:35Z","https://github.com/nuxt/ui/issues/4468",0.7300599,{"description":3225,"labels":3226,"number":3230,"owner":3187,"repository":3188,"state":3204,"title":3231,"updated_at":3232,"url":3233,"score":3234},"### Description\n\nI think a nice addition could be the method `isOpen(id: symbol): boolean` to check if an overlay opened programmatically is currently open.\nCan I get this assigned? I would like to open a PR about this :)\n\n### Additional context\n\n_No response_",[3227,3228,3229],{"name":3181,"color":3182},{"name":3184,"color":3185},{"name":3217,"color":3218},4007,"[useOverlay] add `isOpen` method","2025-05-01T16:48:42Z","https://github.com/nuxt/ui/issues/4007",0.73696566,{"description":3236,"labels":3237,"number":3240,"owner":3187,"repository":3188,"state":3204,"title":3241,"updated_at":3242,"url":3243,"score":3244},"### Description\n\nCurrently when I use useOverlay and pass props it says props is type any.\nby adding `satisfies InstanceType\u003Ctypeof COMPONENT>[\"$props\"]` it gets the right types.\n\nBut it should work out of the box. Could the typesafety for props be implemented?\n\ncurrent solution\n```\n useOverlay()\n .create(COMPONENT, {\n props: {\n id: id,\n onUpdated() {\n...\n },\n } satisfies InstanceType\u003Ctypeof COMPONENT>[\"$props\"],\n })\n .open();\n```\n\n### Additional context\n\nSomething like this could create type safety\n\n```\nfunction createTypedOverlay\u003CT extends new (...args: any) => any>(\n component: T,\n options: {\n props: InstanceType\u003CT>[\"$props\"];\n [key: string]: any;\n }\n) {\n return useOverlay().create(component, options);\n}\n```",[3238,3239],{"name":3213,"color":3214},{"name":3184,"color":3185},3915,"Typesafety on useOverlay props","2025-05-01T20:57:51Z","https://github.com/nuxt/ui/issues/3915",0.7433104,{"description":3246,"labels":3247,"number":3251,"owner":3187,"repository":3252,"state":3204,"title":3253,"updated_at":3254,"url":3255,"score":3256},"Don't we have too many links in Community section compared to `Resources`, `Company`...?",[3248],{"name":3249,"color":3250},"question","ff1ab2",825,"nuxt.com","[Community] Too many links","2022-11-17T11:43:46Z","https://github.com/nuxt/nuxt.com/issues/825",0.74546534,{"description":3258,"labels":3259,"number":3271,"owner":3187,"repository":3188,"state":3204,"title":3272,"updated_at":3273,"url":3274,"score":3275},"### Environment\n\nOperating System: Windows 11\nNode Version: v22.14.0\nNuxt Version: 3.17.4\nNitro Version: 2.11.12\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.3\n\n### Description\n\nHi,\nWhen I use the mouseenter and mouseleave or mouseover and mouseout events, the following error appears and the events don't work:\n\n\"[Vue warn]: Extraneous non-emits event listeners (mouseenter, mouseleave) were passed to component but could not be automatically inherited because component renders fragment or text root nodes. If the listener is intended to be a component custom event listener only, declare it using the emits option.\"\n\nWhat should I do? Can you help me?\n",[3260,3261,3264,3265,3268],{"name":3213,"color":3214},{"name":3262,"color":3263},"needs reproduction","CB47CF",{"name":3184,"color":3185},{"name":3266,"color":3267},"nuxt/ui-pro","00dc82",{"name":3269,"color":3270},"closed-by-bot","ededed",4268,"Extraneous non-emits event listeners (mouseenter, mouseleave) on UDashboardSidebar component","2025-08-15T02:16:25Z","https://github.com/nuxt/ui/issues/4268",0.74583757,{"description":3277,"labels":3278,"number":3284,"owner":3187,"repository":3188,"state":3204,"title":3285,"updated_at":3286,"url":3287,"score":3288},"### Description\r\n\r\nI see that TransitionRoot has some events but how could I detect them from UModal or other overlays? ",[3279,3281,3282],{"name":3249,"color":3280},"d876e3",{"name":3269,"color":3270},{"name":3283,"color":3270},"stale",1304,"Detecting transition events on Overlays ","2025-06-19T02:12:55Z","https://github.com/nuxt/ui/issues/1304",0.74822766,{"description":3290,"labels":3291,"number":3299,"owner":3187,"repository":3188,"state":3204,"title":3300,"updated_at":3301,"url":3302,"score":3303},"### Environment\n\n```\nNuxt project info: 4:13:17 PM\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.16.0\n- Nuxt Version: 3.13.2\n- CLI Version: 3.14.0\n- Nitro Version: 2.9.7\n- Package Manager: pnpm@9.7.1\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n```\n\n### Version\n\n2.18.7\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/button\n\n### Description\n\n\nMy issue is pretty close to https://github.com/nuxt/ui/issues/468.\n\nIt's when you switch between different types of props on a component document that this issue occurs, the first time you enter it no such issue occurs.\n\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3292,3293,3296],{"name":3213,"color":3214},{"name":3294,"color":3295},"documentation","0075ca",{"name":3297,"color":3298},"duplicate","cfd3d7",2429,"DOCS: You should use slots with \u003CContentRenderer>","2024-10-21T10:20:28Z","https://github.com/nuxt/ui/issues/2429",0.7503868,{"description":3305,"labels":3306,"number":3309,"owner":3187,"repository":3310,"state":3204,"title":3311,"updated_at":3312,"url":3313,"score":3314},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.15.4\n- CLI Version: 3.22.4\n- Nitro Version: 2.11.3\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: devtools, compatibilityDate\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-4czkz34t?file=components%2FMyComponent.vue,test%2FMyComponent.test.js\n\n### Describe the bug\n\nAfter using `setProps` in a component mounted with `mountSuspended`, using `$emit` inside a method will emit the event twice, which can be checked with `wrapper.emitted()`. This behaviour does not exist when using `mount()`. Please see reproduction link.\n\nA workaround is to use the `$emit` directly in the `@click` attribute, like this:\n\n```\n\u003Cbutton @click=\"$emit('test', 'a')\">test\u003C/button>\n```\n\nBut this is not sufficient if a method needs to be called that does other things as well besides emitting.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3307],{"name":3201,"color":3308},"5D08F5",1176,"test-utils","Component mounted with mountSuspended emits events twice after setProps was called","2025-06-17T09:02:32Z","https://github.com/nuxt/test-utils/issues/1176",0.7562284,["Reactive",3316],{},["Set"],["ShallowReactive",3319],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fSmwNJ6QOSL-EnZtxlAgjSFY1hiaXjk6yqNw70RS8vTQ":-1},"/nuxt/ui/3842"]