`\n\n```vue\n\u003Cscript setup lang=\"ts\">\nconst items = ref([ 'foo', 'bar' ])\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUInputMenu :items=\"items\" multiple @change=\"console.log('change')\" />\n\u003C/template>\n```\n\n### Description\n\nChange event on UInputMenu is not triggered by clicking on the delete-icon.\n\nSeems like deleting by clicking the item in the list like mentioned here https://github.com/nuxt/ui/issues/3756 is fixed but clicking the delete-icon still wont triggers the @change event\n\n### Additional context\n\nwhile trying to recreate the issue in codesandbox i also got this error\n\n### Logs\n\n```shell-script\nUncaught TypeError: Cannot read properties of undefined (reading 'filter')\n at onRemoveTag (/_nuxt/@fs/project/workspace/node_modules/.pnpm/@nuxt+ui@3.0.2_embla-carousel@8.5.2_typescript@5.8.2_vite@6.2.4/node_modules/@nuxt/ui/dist/runtime/components/InputMenu.vue:182:42)\n at callWithErrorHandling (runtime-core.esm-bundler.js?v=d5312b36:197:19)\n at callWithAsyncErrorHandling (runtime-core.esm-bundler.js?v=d5312b36:204:17)\n at emit (runtime-core.esm-bundler.js?v=d5312b36:6406:5)\n at runtime-core.esm-bundler.js?v=d5312b36:8115:45\n at Object.handleRemoveTag [as onRemoveValue] (/_nuxt/@fs/project/workspace/node_modules/.pnpm/reka-ui@2.1.1_typescript@5.8.2_vue@3.5.13/node_modules/reka-ui/dist/TagsInput/TagsInputRoot.js?v=d5312b36:56:9)\n at handleDelete (/_nuxt/@fs/project/workspace/node_modules/.pnpm/reka-ui@2.1.1_typescript@5.8.2_vue@3.5.13/node_modules/reka-ui/dist/TagsInput/TagsInputItemDelete.js?v=d5312b36:24:15)\n at callWithErrorHandling (runtime-core.esm-bundler.js?v=d5312b36:197:19)\n at callWithAsyncErrorHandling (runtime-core.esm-bundler.js?v=d5312b36:204:17)\n at HTMLButtonElement.invoker (runtime-dom.esm-bundler.js?v=d5312b36:720:5)\n```",[2036,2037,2040],{"name":1985,"color":1986},{"name":2038,"color":2039},"duplicate","cfd3d7",{"name":2005,"color":2006},3890,"UInputMenu change event is not triggered by clicking delete-icon (when multiple=true)","2025-04-14T13:56:50Z","https://github.com/nuxt/ui/issues/3890",0.7534876,{"description":2047,"labels":2048,"number":2051,"owner":1991,"repository":1992,"state":2028,"title":2052,"updated_at":2053,"url":2054,"score":2055},"### Environment\n\n- Operating System: `Linux`\n- Node Version: `v20.16.0`\n- Nuxt Version: `3.16.1`\n- CLI Version: `3.23.1`\n- Nitro Version: `2.11.7`\n- Package Manager: `pnpm@10.6.3`\n- Builder: `-`\n- User Config: `modules`, `devtools`, `css`, `vite`, `colorMode`, `nitro`, `future`, `compatibilityDate`, `hub`, `app`, `schemaOrg`, `i18n`\n- Runtime Modules: `@nuxthub/core@0.8.18`, `@nuxt/ui@3.0.0`, `@nuxtjs/i18n@9.3.2`, `@nuxtjs/seo@3.0.1`, `nuxt-auth-utils@0.5.17`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.16.1\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/dry-sun-8ddkqr\n\n### Description\n\nThe events of the `USelectMenu` do not work as intended. As you can see in the reproduction, the `change` event of the `UForm` is expected to be emitted every time you select/deselect/create an item, but instead it's emitted only a few seemingly random times.\n\nSwitching to the `input` event on the form has the same random behavior.\n\nI am also surprised programmatically changing the list of values doesn't trigger the `update` event on the `USelectMenu`, but that could be by design and is not really the blocking issue here.\n\nMy reproduction code is a simplification of my real code. It is very similar to the documentation example for creating items, main difference is the multi selection. However the issue also occurs without multi selection.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2049,2050],{"name":1985,"color":1986},{"name":2005,"color":2006},3660,"`USelectMenu` doesn't emit `UForm`.`change` as expected","2025-04-04T16:14:05Z","https://github.com/nuxt/ui/issues/3660",0.7558324,{"description":2057,"labels":2058,"number":2064,"owner":1991,"repository":1992,"state":2028,"title":2065,"updated_at":2066,"url":2067,"score":2068},"### Description\n\nThere is currently no easy way to know what state the modal is in. Adding a `toggle` method would make life very much easier.\n\nI'm willing to make a PR\n\n### Additional context\n\n_No response_",[2059,2062,2063],{"name":2060,"color":2061},"enhancement","a2eeef",{"name":2005,"color":2006},{"name":1988,"color":1989},3720,"feat: add toogle for useOverlay","2025-04-09T15:26:14Z","https://github.com/nuxt/ui/issues/3720",0.774219,{"description":2070,"labels":2071,"number":2073,"owner":1991,"repository":1992,"state":2028,"title":2074,"updated_at":2075,"url":2076,"score":2077},"### For what version of Nuxt UI are you asking this question?\n\nv2.x\n\n### Description\n\n### Description\nHi there,\n\nIn many of the projects I’m working on, I need to display a limited number of items in the command palette when no search is performed and show more items when a search is initiated.\n\nCurrent Issue\nThe `resultLimit` currently controls how many search results are shown, but I want to decouple the initial number of displayed items from the search result limit. Specifically, I want to:\n\n- Display 5 items by default when no search is performed.\n- Increase the number of displayed items to 20 when a search is initiated, controlled by the `resultLimit`, without affecting the initial state.\n- When attempting to conditionally control this behavior using a computed property, the feature does not work as expected.\n\n Versions\n\n@nuxt/ui: ^2.18.2\nnuxt: ^3.12.4\n\nExample\n\n```Javascript\n\u003Ctemplate>\n \u003CUCommandPalette\n command-attribute=\"title\"\n :fuse=\"{\n resultLimit: computedResultLimit\n }\"\n />\n\u003C/template>\n\n\u003Cscript setup>\nconst searchTerm = ref('');\n\nconst computedResultLimit = computed(() => {\n if (!searchTerm.value) {\n return 5;\n }\n return 20;\n});\n\u003C/script>\n```\n",[2072],{"name":2002,"color":2003},2393,"Command Palette: Specific Item Display with Conditional resultLimit Behavior","2024-10-16T09:31:26Z","https://github.com/nuxt/ui/issues/2393",0.7752692,{"description":2079,"labels":2080,"number":2084,"owner":1991,"repository":1992,"state":2028,"title":2085,"updated_at":2086,"url":2087,"score":2088},"### Environment\n\n------------------------------\n- Operating System: Windows_NT\n- Node Version: v20.10.0\n- Nuxt Version: 3.15.2\n- CLI Version: 3.20.0\n- Nitro Version: 2.10.4\n- Package Manager: yarn@4.5.0\n- Builder: -\n- User Config: app, site, modules, ui, imports, nitro, i18n, devtools, runtimeConfig, experimental, future, content\n- Runtime Modules: @nuxt/ui-pro@3.0.0-alpha.11, @nuxtjs/seo@2.1.0, @nuxt/content@3.0.0, @nuxtjs/i18n@9.1.2, @nuxt/scripts@0.9.5, @nuxt/fonts@0.10.3\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.11\n\n### Reproduction\n\nThe reproduction uses the documentation's Toast usage example from https://ui3.nuxt.dev/components/toast (the `showToast` function) adjusted to the needs of my project (version tracker):\n\n```ts\nconst {data, error} = await useAsyncData('versions', async () => {\n\tthrow createError({statusCode: '404'}) // this is done to simulate an error to trigger the toast\n\treturn {data1: [], data2: []}\n})\n\nconst toast = useToast()\nfunction showToast(what: string, prop?: string) {\n\ttoast.add({\n\t\ttitle: 'Failed to fetch '+what + ' version information.',\n\t\tdescription: versionData[prop]?.[0]?.version ? 'Showing potentially stale data until next status update' : 'Retrying status fetch in 30 seconds.',\n\t\ticon: 'i-lucide-x',\n\t\tcolor: 'error',\n\t\tduration: 10000\n\t})\n}\nonNuxtReady(()=>{\n\tif (error.value) {\n\t\tshowToast('Data1', 'data1')\n\t\tshowToast('Data2', 'data2')\n\t}\n})\n```\n\n### Description\n\nWhen 2 toasts are added close to one another (in the execution time), sometimes they don't both get rendered, even though the `add` is called. The chance of one of them not getting rendered increases the closer they are.\n\nFor example, in the reproduction, the second toast almost never gets rendered. \n\nMeanwhile, having the toast function in a catch clause (with a `createError` in the try clause) has higher chances of rendering both toasts, but still inconsistently.\n\n### Additional context\n\nThis image shows only the first toast gets rendered (the white border indicates end of page):\n\n\n\n### Logs\n\n```shell-script\n\n```",[2081,2082,2083],{"name":1985,"color":1986},{"name":2038,"color":2039},{"name":2005,"color":2006},3166,"Multiple toast creations do not consistently render equivalent number of toasts","2025-01-23T20:11:47Z","https://github.com/nuxt/ui/issues/3166",0.77915186,{"description":2090,"labels":2091,"number":2094,"owner":1991,"repository":1992,"state":2028,"title":2095,"updated_at":2096,"url":2097,"score":2098},"### Environment\n\n- Operating System: Linux\n- Node Version: v23.4.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: bun@1.2.1\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, runtimeConfig, auth, pinia, fonts, css, ui, app\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.12, @sidebase/nuxt-auth@0.10.0, @nuxt/fonts@0.10.3, @pinia/nuxt@0.9.0\n- Build Modules: -\n\n\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.12\n\n### Reproduction\n\nhttps://github.com/StefanH-AT/NuxtUi3-Shortcut-Meta\n\n### Description\n\n[According to the docs](https://ui3.nuxt.dev/composables/define-shortcuts#usage), `meta` is supposed to be translated to `Ctrl`, but on Linux, the Linux Meta key, which is the same as the Windows key, is detected.\n\nI find the usage of the word \"meta\" confusing due to this double meaning. Meta is commonly used to refer to the Windows aka Super aka Meta key, but not as Control\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2092,2093],{"name":1985,"color":1986},{"name":2005,"color":2006},3220,"Meta keyboard shortcut maps to system meta (\"Windows\") key on linux instead of Ctrl","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/3220",0.7816064,["Reactive",2100],{},["Set"],["ShallowReactive",2103],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"pb1jCqYdJs-9waES23aod5X9H8Ux1SoKOeJ1W9EPypg":-1},"/nuxt/ui/3876"]