\n```\n\n### Additional context\n\nhttps://github.com/nuxt/ui/blob/c00f6e8cdfd88eeba58812b78d94a2326c13f164/src/runtime/components/Checkbox.vue#L98",[2876,2879,2880],{"name":2877,"color":2878},"enhancement","a2eeef",{"name":2860,"color":2861},{"name":2863,"color":2864},4176,"UCheckbox emits both `@input` and `@change` events on toggle, causing duplicate validations","2025-05-19T01:23:36Z","https://github.com/nuxt/ui/issues/4176",0.7333715,{"description":2887,"labels":2888,"number":2891,"owner":2866,"repository":2867,"state":2868,"title":2892,"updated_at":2893,"url":2894,"score":2895},"",[2889,2890],{"name":2857,"color":2858},{"name":2860,"color":2861},2346,"[Popover] Hover mode not working on mobile","2024-11-06T17:02:41Z","https://github.com/nuxt/ui/issues/2346",0.7459284,{"description":2897,"labels":2898,"number":2899,"owner":2866,"repository":2900,"state":2868,"title":2901,"updated_at":2902,"url":2903,"score":2904},"My icon file directory is nested, which means I'm creating multiple `customCollections`, like this: \n\n\nIs there a simpler way to write it?",[],316,"icon","Local custom nested folder usage issues","2025-03-16T06:02:57Z","https://github.com/nuxt/icon/issues/316",0.74601704,{"description":2906,"labels":2907,"number":2910,"owner":2866,"repository":2867,"state":2911,"title":2912,"updated_at":2913,"url":2914,"score":2915},"### Environment\n\n- Operating System: Darwin\n- Node Version: v23.4.0\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.7\n- Package Manager: bun@1.2.5\n- Builder: -\n- User Config: devtools, modules, imports, components, css, compatibilityDate, experimental, future\n- Runtime Modules: @nuxt/ui@3.0.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/recursing-browser-klwx46\n\n### Description\n\nWhen a `SelectMenu` is wrapped in a custom component which is then consumed by `FormField` validation is triggered for an instant before the component goes back to its valid state.\n\nI've tried to debug a bit and I think it's related to the fact that the `SelectMenu` uses `Input` and that input is firing a `change` event because it uses `useFormField`, even though that particular input should not be considered the \"form field\" in this instance.\n\n### Additional context\n\nhttps://github.com/user-attachments/assets/75e8c84f-612e-48f0-bf9e-dcc1fe95ffcd\n\nI'd like to open a PR and fix this myself but I'm not sure what the best approach it. Maybe `Input` could take a prop that allows it to not fire form events? i.e. `ignore-form-events=\"true\"` so the SelectMenu would use it. This could also apply for other components that use primitive form inputs inside them (Command, InputMenu) etc.\n\n### Logs\n\n```shell-script\n\n```",[2908,2909],{"name":2857,"color":2858},{"name":2860,"color":2861},3736,"closed","[USelectMenu] Validation events are triggered before change when wrapped in a custom component","2025-05-14T17:24:48Z","https://github.com/nuxt/ui/issues/3736",0.6396249,{"description":2917,"labels":2918,"number":2928,"owner":2866,"repository":2867,"state":2911,"title":2929,"updated_at":2930,"url":2931,"score":2932},"### Environment\n\nNuxt project info: (copied to clipboard) nuxi 10:36:44\n\n------------------------------\n- Operating System: Windows_NT\n- Node Version: v20.9.0\n- Nuxt Version: 3.16.0\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.11\n- Package Manager: npm@10.9.0\n- Builder: -\n- User Config: devtools, modules, css, future, compatibilityDate, experimental, nitro, sourcemap, ssr, spaLoadingTemplate, runtimeConfig\n- Runtime Modules: @nuxt/ui@3.1.1, @nuxtjs/mdc@0.15.0, @vueuse/nuxt@13.1.0\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.1\n\n### Reproduction\n\n\nInput Menu Send an event when using @Change\n\n\n\nBut it is scheduled to send a value and this generates the error in console\n\n\n\n\n\n### Description\n\nhttps://github.com/user-attachments/assets/3fdd5798-3f77-45e0-a86b-18a2195219f2\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2919,2920,2923,2924,2925],{"name":2857,"color":2858},{"name":2921,"color":2922},"needs reproduction","CB47CF",{"name":2860,"color":2861},{"name":2863,"color":2864},{"name":2926,"color":2927},"closed-by-bot","ededed",4103,"InputMenu Event onChange","2025-05-17T02:08:14Z","https://github.com/nuxt/ui/issues/4103",0.71487004,{"description":2934,"labels":2935,"number":2939,"owner":2866,"repository":2867,"state":2911,"title":2940,"updated_at":2941,"url":2942,"score":2943},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v22.13.0\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.7\n- Package Manager: bun@1.2.4\n- Builder: -\n- User Config: compatibilityDate, devtools, runtimeConfig, nitro, routeRules, modules, ui, supabase, site, feed, sitemap, robots, schemaOrg, image, hub\n- Runtime Modules: @nuxt/ui@3.0.1, @nuxtjs/supabase@1.5.0, @vueuse/nuxt@13.0.0, @nuxt/image@1.10.0, @nuxthub/core@0.8.18, @nuxtjs/sitemap@7.2.9, nuxt-module-feed@1.1.4, @nuxtjs/robots@5.2.8, nuxt-schema-org@5.0.4, nuxt-link-checker@4.3.0\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.1\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/adoring-gates-fd8q9s\n\n### Description\n\n## Expected behaviour\nValidation should trigger when a user adds or removes items from an input menu that has the `multiple` prop\n\n## Actual behaviour\nValidation seems to trigger when the input menu is opened or closed, but not when items are removed\n\n## Reproduction\n1. Use the codesandbox provided\n2. Add all 4 items to the input\n3. Validation should trigger saying 3 max\n4. Remove an item\n5. **Validation error persists, when it should be gone**\n6. Remove all the items\n7. Add a single item\n8. Remove them item\n9. **Validation error should appear stating 1 item min, but it doesn't**\n\n### Additional context\n\n## Screen capture\n\nhttps://github.com/user-attachments/assets/fccda9b1-2837-4b7d-85ad-5d63480582a1\n\n### Logs\n\n```shell-script\n\n```",[2936,2937,2938],{"name":2857,"color":2858},{"name":2860,"color":2861},{"name":2863,"color":2864},3726,"Form validation with InputMenu doesn't trigger when expected","2025-04-08T19:48:00Z","https://github.com/nuxt/ui/issues/3726",0.7193223,{"description":2945,"labels":2946,"number":2949,"owner":2866,"repository":2950,"state":2911,"title":2951,"updated_at":2952,"url":2953,"score":2954},"Redirect to `/projects` public page instead\n\nBlocked by #403 ",[2947],{"name":2877,"color":2948},"1ad6ff",402,"nuxt.com","Beta page integration `/beta`","2022-06-07T09:41:42Z","https://github.com/nuxt/nuxt.com/issues/402",0.73010206,{"description":2956,"labels":2957,"number":2961,"owner":2866,"repository":2866,"state":2911,"title":2962,"updated_at":2963,"url":2964,"score":2965},"I think there is a bug in Nuxt 2.4.x in transition.\r\n\r\nExample in about.vue template:\r\n\r\n```\r\n \u003Ctransition\r\n appear //---> this never work\r\n v-on:before-enter=\"beforeEnter\"\r\n v-on:enter=\"enter\"\r\n v-on:after-enter=\"afterEnter\"\r\n \r\n v-on:leave=\"leave\">\r\n ....\r\n \u003C/transition>\r\n```\r\n\r\nIn script:\r\n\r\n``` \r\n transition: {\r\n mode: 'out-in',\r\n css: false,\r\n beforeEnter (el) {\r\n console.log('before in transition object') // works\r\n },\r\n enter (el, done) {\r\n console.log('enter in transition object') // works\r\n },\r\n afterEnter (el) {\r\n console.log('after enter in transition object') // works\r\n },\r\n leave (el, done) {\r\n console.log('leave in transition object') // works\r\n done()\r\n }\r\n },\r\n \r\n methods: {\r\n // https://nuxtjs.org/api/pages-transition\r\n // https://vuejs.org/v2/guide/transitions.html#JavaScript-Hooks\r\n beforeEnter (el) {\r\n console.log('before in methods object') // never executed\r\n },\r\n enter (el, done) {\r\n console.log('enter in methods object') // never executed\r\n },\r\n afterEnter (el) {\r\n console.log('after enter in transition object') // never executed\r\n },\r\n leave (el, done) {\r\n console.log('leave in methods object') // never executed\r\n },\r\n }\r\n```\r\nIf you **remove** all the methods in the `methods object`, you get these errors:\r\n\r\n> commons.app.js:9837 [Vue warn]: Property or method \"beforeEnter\" is\r\n> not defined on the instance but referenced during render. Make sure\r\n> that this property is reactive, either in the data option, or for\r\n> class-based components, by initializing the property. See:\r\n> https://vuejs.org/v2/guide/reactivity.html#Declaring-Reactive-Properties.\r\n> \r\n> \r\n> found in\r\n> \r\n> ---> \u003CPages/about.vue> at pages/about.vue\r\n> \u003CNuxt>\r\n> \u003CLayouts/default.vue> at layouts/default.vue\r\n> \u003CRoot> commons.app.js:9837 [Vue warn]: Property or method \"enter\" is not defined on the instance but referenced during render.\r\n> Make sure that this property is reactive, either in the data option,\r\n> or for class-based components, by initializing the property. See:\r\n> https://vuejs.org/v2/guide/reactivity.html#Declaring-Reactive-Properties.\r\n> \r\n> found in\r\n> \r\n> ---> \u003CPages/about.vue> at pages/about.vue\r\n> \u003CNuxt>\r\n> \u003CLayouts/default.vue> at layouts/default.vue\r\n> \u003CRoot>\r\n> \r\n> and so on...\r\n\r\nIs it a bug or something else I am missing??\r\n\r\nEDIT:\r\n\r\nThe entire code structure in my pages/about.vue:\r\n\r\n```\r\n\u003Ctemplate>\r\n\r\n \u003Ctransition\r\n v-on:before-enter=\"beforeEnter\"\r\n v-on:enter=\"enter\"\r\n v-on:after-enter=\"afterEnter\"\r\n v-on:leave=\"leave\">\r\n\r\n \u003C!-- article -->\r\n \u003Cdiv class=\"row\" v-if=\"post\">\r\n\r\n ///\r\n\r\n \u003C/div>\r\n \u003C!-- article -->\r\n\r\n \u003C/transition>\r\n\u003C/template>\r\n\r\n\u003Cscript>\r\nimport $ from 'jquery'\r\n\r\nexport default {\r\n name: 'slug',\r\n data () {\r\n return {\r\n post: null\r\n }\r\n },\r\n mounted () {\r\n //\r\n },\r\n transition: {\r\n mode: 'out-in',\r\n css: false,\r\n beforeEnter (el) {\r\n console.log('before in transition object')\r\n },\r\n enter (el, done) {\r\n console.log('enter in transition object')\r\n done()\r\n },\r\n afterEnter (el) {\r\n console.log('after enter in transition object')\r\n },\r\n leave (el, done) {\r\n console.log('leave in transition object')\r\n done()\r\n }\r\n },\r\n methods: {\r\n // https://nuxtjs.org/api/pages-transition\r\n // https://vuejs.org/v2/guide/transitions.html#JavaScript-Hooks\r\n beforeEnter (el) {\r\n console.log('before in methods object')\r\n },\r\n enter (el, done) {\r\n console.log('enter in methods object')\r\n },\r\n afterEnter (el) {\r\n console.log('after enter in transition object')\r\n },\r\n leave (el, done) {\r\n console.log('leave in methods object')\r\n },\r\n }\r\n}\r\n\u003C/script>\r\n```\r\n\r\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\r\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c8728\">#c8728\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2958],{"name":2959,"color":2960},"2.x","d4c5f9",5111,"JavaScript hooks transition - a bug on pages?","2023-01-18T20:10:40Z","https://github.com/nuxt/nuxt/issues/5111",0.7318185,{"description":2967,"labels":2968,"number":2974,"owner":2866,"repository":2867,"state":2911,"title":2975,"updated_at":2976,"url":2977,"score":2978},"### Description\n\nCurrently, I want to use the InputMenu for URL suggestions. The user can choose whether they want to select one of the suggestions or enter their own URL. There are several InputMenus, which means that the user usually wants to jump to the next field using the tab key. \n\nHowever, this is not so easy with the InputMenu. With `create-items`, the field expects a click or enter to be entered. There is no autocreate. \n\nI have also tried using `update:search-terms`, which worked well as long as the user treated it as a pure input field. However, in this case, no suggestions appear. And if the user selects a suggestion, the VModel is also empty – more precisely, it gets a value and is deleted shortly afterwards.\n\nTherefore, it would be desirable if create-items could be set to transfer the input to the V-Model immediately, or if there was a general mode in which the input field treats the suggestions as optional.\n\n\n\n### Additional context\n\n_No response_",[2969,2970,2971,2972,2973],{"name":2877,"color":2878},{"name":2921,"color":2922},{"name":2860,"color":2861},{"name":2863,"color":2864},{"name":2926,"color":2927},4106,"InputMenu with Autocreate","2025-05-18T02:13:24Z","https://github.com/nuxt/ui/issues/4106",0.73639303,["Reactive",2980],{},["Set"],["ShallowReactive",2983],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fzfL-3p_aZGbamX-EQXwcRx24LQ37aGbii7JeP6fZ91Q":-1},"/nuxt/ui/4139"]