\n \u003C/UTooltip>\n \u003CUDropdownMenu :items=\"[items, actions]\">\n \u003CUButton label=\"Second\" />\n \u003C/UDropdownMenu>\n\u003C/template>\n\n\u003Cscript setup>\nconst actions = [\n {\n label: 'Create team',\n icon: 'i-heroicons-plus-circle'\n },\n {\n label: 'Manage teams',\n icon: 'i-heroicons-cog-8-tooth'\n }\n]\n\nconst items = ref([\n {\n label: 'Profile',\n icon: 'i-lucide-user'\n },\n {\n label: 'Billing',\n icon: 'i-lucide-credit-card'\n },\n {\n label: 'Settings',\n icon: 'i-lucide-cog'\n }\n])\n\u003C/script>\n```\n\n2. Non-Working Example (Dropdown fails):\nRemove the “Fisrt” button and its wrapping UTooltip so that only the dropdown remains:\n\n\n```vue\n\u003Ctemplate>\n \u003C!-- Removed UTooltip and the first button -->\n \u003CUDropdownMenu :items=\"[items, actions]\">\n \u003CUButton label=\"Second\" />\n \u003C/UDropdownMenu>\n\u003C/template>\n\n\u003Cscript setup>\nconst actions = [\n {\n label: 'Create team',\n icon: 'i-heroicons-plus-circle'\n },\n {\n label: 'Manage teams',\n icon: 'i-heroicons-cog-8-tooth'\n }\n]\n\nconst items = ref([\n {\n label: 'Profile',\n icon: 'i-lucide-user'\n },\n {\n label: 'Billing',\n icon: 'i-lucide-credit-card'\n },\n {\n label: 'Settings',\n icon: 'i-lucide-cog'\n }\n])\n\u003C/script>\n```\n\nIn the first scenario, the dropdown opens and displays the items as expected.\n\nIn the second scenario, clicking on the button inside the UDropdownMenu does not open the dropdown.\n\nThe UDropdownMenu should work independently. Removing unrelated components (like the UTooltip with the “Fisrt” button) should not affect its functionality.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2922,2925,2928],{"name":2923,"color":2924},"bug","d73a4a",{"name":2926,"color":2927},"duplicate","cfd3d7",{"name":2929,"color":2930},"v3","49DCB8",3344,"ui","DropdownMenu has a buggy behaviour related with other components","2025-02-19T01:59:03Z","https://github.com/nuxt/ui/issues/3344",0.71191543,{"description":2938,"labels":2939,"number":2948,"owner":2913,"repository":2932,"state":2914,"title":2949,"updated_at":2950,"url":2951,"score":2952},"### Environment\n\n- Operating System: Linux\n- Node Version: v20.9.0\n- Nuxt Version: 3.15.3\n- CLI Version: 3.20.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.13.1\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, css\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.12, @vee-validate/nuxt@4.15.0\n- Build Modules: -\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://stackblitz.com/~/github.com/arpadgabor/nuxt-ui-3-bug\n\nIn case the above link does not work, here is the repo: https://github.com/arpadgabor/nuxt-ui-3-bug\n\n### Description\n\nWhen using the Select and SelectMenu components with vee-validate, especially when there are multiple fields involved, there is a very weird behaviour. Selection does not work correctly, cannot close the dropdown, etc. I've added a recording as well (I keep clicking outside and on the menu options).\n\nhttps://github.com/user-attachments/assets/bc8aa97c-377c-4f57-ab7d-55929f30d97c\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2940,2941,2942,2945],{"name":2923,"color":2924},{"name":2929,"color":2930},{"name":2943,"color":2944},"triage","ffffff",{"name":2946,"color":2947},"stale","ededed",3194,"[Select] Buggy behaviour of Select fields when used with vee-validate","2025-06-12T15:32:10Z","https://github.com/nuxt/ui/issues/3194",0.7160226,{"description":2954,"labels":2955,"number":2961,"owner":2913,"repository":2913,"state":2914,"title":2962,"updated_at":2963,"url":2964,"score":2965},"### Environment\n\nnuxt version 3.8\n\n### Reproduction\n\nwhen i navigating routes content flashes on and off\n\n### Describe the bug\n\n\r\n\r\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2956,2957,2958],{"name":2907,"color":2908},{"name":2910,"color":2911},{"name":2959,"color":2960},"needs reproduction","FBCA04",23918,"suspense is not working nuxt v3.8","2023-11-15T19:19:09Z","https://github.com/nuxt/nuxt/issues/23918",0.71952945,{"description":2967,"labels":2968,"number":2971,"owner":2913,"repository":2913,"state":2914,"title":2972,"updated_at":2973,"url":2974,"score":2975},"### Environment\r\n\r\n------------------------------\r\n- Operating System: `Windows_NT`\r\n- Node Version: `v16.16.0`\r\n- Nuxt Version: `3.3.3`\r\n- Nitro Version: `2.3.2`\r\n- Package Manager: `npm@8.11.0`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-boqtvs?file=app.vue\r\n\r\n### Describe the bug\r\n\r\nWhen navigating between pages, the child page component is rendered two times and the first time with null property values and the second time with the actual value.\r\nAt the moment the only workaround is to check in the setup routine if the prop is defined and return an empty hyperscript block.\r\nBesides adding additional checks in the template, the typings for template vars are not present anymore.\r\n\r\n**Workaround**\r\n```typescript\r\n// ...\r\nsetup(props) {\r\n // todo: remove this when this is fixed in vue/nuxt\r\n if (!props.entity) {\r\n return () => h('div', []);\r\n }\r\n\r\n console.log(props.entity.attribute); // attempt to access property of undefined without previous check :/\r\n\r\n // ......\r\n},\r\n// ....\r\n```\r\n\r\n### Additional context\r\n\r\nhttps://github.com/nuxt/nuxt/issues/15035\r\n### Logs\r\n\r\n_No response_",[2969,2970],{"name":2907,"color":2908},{"name":2910,"color":2911},20309,"Child Page- 2 times rendered (Properties: undefined than actual value)","2023-04-16T16:21:03Z","https://github.com/nuxt/nuxt/issues/20309",0.72234434,{"labels":2977,"number":2982,"owner":2913,"repository":2913,"state":2914,"title":2983,"updated_at":2984,"url":2985,"score":2986},[2978,2979],{"name":2910,"color":2911},{"name":2980,"color":2981},"2.x","d4c5f9",7276,"Vuex mutations with enumerable properties","2023-01-22T15:34:50Z","https://github.com/nuxt/nuxt/issues/7276",0.7223566,{"description":2988,"labels":2989,"number":2995,"owner":2913,"repository":2913,"state":2914,"title":2996,"updated_at":2997,"url":2998,"score":2999},"### Environment\r\n\r\n\r\n\r\n------------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v18.17.1\r\n- Nuxt Version: 3.7.0\r\n- CLI Version: 3.7.2\r\n- Nitro Version: 2.6.2\r\n- Package Manager: yarn@1.22.19\r\n- Builder: -\r\n- User Config: vue, site, imports, image, runtimeConfig, app, css, typescript, modules, vueuse, colorMode, vite, elementPlus, plugins\r\n- Runtime Modules: @vueuse/nuxt@10.4.1, @pinia/nuxt@0.4.11, @element-plus/nuxt@1.0.5, @nuxtjs/color-mode@3.3.0, @nuxtjs/color-mode@3.3.0, @unocss/nuxt@0.55.1, @nuxt/image@1.0.0-rc.1, nuxt-lodash@2.5.0, nuxt-simple-sitemap@3.2.6, nuxt-swiper@1.2.2\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nno need\r\n\r\n### Describe the bug\r\n\r\nAfter running 'run build' and executing it with Node.js, an error occurred.\r\nWhen I use 'dev', it can successfully fetch data.\r\n[nuxt] [request error] [unhandled] [500] Cannot read properties of null (reading 'allow_product')\r\nallow_product in Front\r\n```js\r\nconst Front = setFront() \r\nif (!Front) {\r\n const result = await getSetting()\r\n Front.value = result.data\r\n}\r\n```\r\nI tried using state management to reduce duplicate requests and save expenses.\r\nI'm not sure if there's a better way to do it.\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2990,2991,2992,2993],{"name":2907,"color":2908},{"name":2910,"color":2911},{"name":2959,"color":2960},{"name":2994,"color":2947},"closed-by-bot",23025,"[bug] cant fetch data","2023-09-14T01:47:28Z","https://github.com/nuxt/nuxt/issues/23025",0.7257437,{"description":3001,"labels":3002,"number":3005,"owner":2913,"repository":2913,"state":2914,"title":3006,"updated_at":3007,"url":3008,"score":3009},"### Environment\n\n- Operating System: `Windows_NT`\r\n- Node Version: `v14.18.1`\r\n- Nuxt Version: `3.3.1`\r\n- Nitro Version: `-`\r\n- Package Manager: `pnpm@7.25.0`\r\n- Builder: `vite`\r\n- User Config: `modules`, `unocss`, `css`, `content`, `devtools`\r\n- Runtime Modules: `@nuxt/content@2.5.2`, `@unocss/nuxt@0.49.8`, `@vueuse/nuxt@9.13.0`, `@nuxt/devtools@0.2.5-27988848.51397f9`\r\n- Build Modules: `-`\n\n### Reproduction\n\n\"@iconify/json\": \"^2.2.27\",\r\n \"@kaivanwong/eslint-config\": \"0.13.14\",\r\n \"@nuxt/content\": \"^2.4.3\",\r\n \"@nuxt/devtools\": \"npm:@nuxt/devtools-edge@latest\",\r\n \"@unocss/nuxt\": \"^0.49.8\",\r\n \"@unocss/reset\": \"^0.49.8\",\r\n \"@vueuse/core\": \"^9.13.0\",\r\n \"@vueuse/nuxt\": \"^9.13.0\",\r\n \"eslint\": \"^8.35.0\",\r\n \"nuxt\": \"^3.3.1\",\r\n \"sass\": \"^1.58.3\"\n\n### Describe the bug\n\nCannot read property 'name' of undefined\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3003,3004],{"name":2907,"color":2908},{"name":2910,"color":2911},19840,"Cannot read property 'name' of undefined","2023-03-21T09:01:02Z","https://github.com/nuxt/nuxt/issues/19840",0.72760975,{"labels":3011,"number":3015,"owner":2913,"repository":2913,"state":2914,"title":3016,"updated_at":3017,"url":3018,"score":3019},[3012,3013,3014],{"name":2946,"color":2944},{"name":2910,"color":2911},{"name":2980,"color":2981},7552,"multiple nuxt instances in layout","2023-01-22T15:36:01Z","https://github.com/nuxt/nuxt/issues/7552",0.7279261,{"labels":3021,"number":3025,"owner":2913,"repository":2913,"state":2914,"title":3026,"updated_at":3027,"url":3028,"score":3029},[3022,3023,3024],{"name":2946,"color":2944},{"name":2910,"color":2911},{"name":2980,"color":2981},10102,"Cannot read properties of undefined (reading '_isDestroyed')","2024-03-11T18:59:31Z","https://github.com/nuxt/nuxt/issues/10102",0.7289393,["Reactive",3031],{},["Set"],["ShallowReactive",3034],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$feBSCm1RxD8GBnOrPiMeTjmLhhPMsqS7Wx-EQmaFYhYg":-1},"/nuxt/ui/3725"]