\r\n \u003C/UDropdown>\r\n \u003C/template>\r\n\r\n \u003C/UTable>\r\n \u003C/li>`\r\n\r\nThis renders correctly and works wonderfully. The only issue is when I use the \"select\" feature, the two tables sometimes interact where they shouldn't. \r\n\r\nI see this happen when table 1 (that has 5 elements) when I select 2 elements from it, table 2 thinks all elements in table 2 have been selected. This probably has to do with a check to see if the number of selected elements match the number of elements in the table (to see if all elements are selected and change the select icon accordingly). However, when there are two separate tables, they should act independently. \r\n\r\nPicture for reference:\r\n\r\n\r\n\r\n### Describe the bug\r\n\r\nTables that are inside a list and are expected to behave independently are interacting with one another through the SELECT feature.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3167,3170],{"name":3168,"color":3169},"3.x","29bc7f",{"name":3171,"color":3172},"pending triage","E99695",25135,"closed","Table \"Select all\" gets confused when tables are inside a list","2024-01-10T14:21:12Z","https://github.com/nuxt/nuxt/issues/25135",0.73782605,{"description":3180,"labels":3181,"number":3189,"owner":3143,"repository":3159,"state":3174,"title":3190,"updated_at":3191,"url":3192,"score":3193},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.11.0\n- Nuxt Version: 3.17.1\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.11\n- Package Manager: npm@11.3.0\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, css, runtimeConfig, ui\n- Runtime Modules: @nuxt/ui@3.1.0, @formkit/auto-animate/nuxt@0.8.2\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.0\n\n### Reproduction\n\n-\n\n### Description\n\nAfter upgrading from v3.0.2 to v3.1.0 I'm missing types for event binding directives and intellisense/automcomplete for attributes of all Nuxt UI components. Below I added a specific example for the Table component, but this happens to all components. I have removed node_modules, reinstalled, cleared the .nuxt and .output directories, and tried setting up a new project as well (using `npx nuxi init -t ui \u003Cmy-app>`).\n\nMissing types on event binding directives:\n\u003Cimg width=\"712\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/b3bb862c-16aa-4deb-aa12-c07211034f9b\" />\n\nMissing autocomplete:\n\u003Cimg width=\"487\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/8a851f0a-5894-41ae-8cdf-3f2f51d2ab52\" />\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3182,3185,3186],{"name":3183,"color":3184},"bug","d73a4a",{"name":3156,"color":3157},{"name":3187,"color":3188},"triage","ffffff",4029,"Where are all the types? v3.0.2 -> v3.1.0 upgrade","2025-04-30T12:20:42Z","https://github.com/nuxt/ui/issues/4029",0.74546456,{"description":3195,"labels":3196,"number":3198,"owner":3143,"repository":3159,"state":3174,"title":3199,"updated_at":3200,"url":3201,"score":3202},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v20.12.0\r\n- Nuxt Version: 3.10.0\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@10.5.0\r\n- Builder: -\r\n- User Config: devtools, modules\r\n- Runtime Modules: @nuxt/ui@2.18.6\r\n- Build Modules: -\n\n### Version\n\n2.18.6\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/k6rsz6?file=%2Fapp.vue%3A1%2C1\n\n### Description\n\nI'm trying to add types for a `ref` to a `UForm` component, but when I tried to use the `setErrors` method there was the following typescript error:\r\n\r\n```\r\nProperty 'setErrors' does not exist on type\r\n'CreateComponentPublicInstanceWithMixins\u003CReadonly\u003CExtractPropTypes\u003C{ schema: { type: PropType\u003CZodSchema> | PropType\u003CYupObjectSchema\u003Cany>> | PropType\u003CJoiSchema> | PropType\u003Cany>; default: any; }; state: { type: ObjectConstructor; required: true; }; validate: { ...; }; validateOn: { ...; }; }>> & Readonly\u003C...>, ... 24 m...'.\r\nDid you mean 'errors'?\r\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3197],{"name":3183,"color":3184},2292,"Property 'setErrors' does not exist on type","2024-10-06T17:50:16Z","https://github.com/nuxt/ui/issues/2292",0.7547515,{"description":3204,"labels":3205,"number":3209,"owner":3143,"repository":3159,"state":3174,"title":3210,"updated_at":3211,"url":3212,"score":3213},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.11.0\n- Nuxt Version: 4.0.3\n- CLI Version: 3.27.0\n- Nitro Version: 2.12.4\n- Package Manager: pnpm@10.14.0\n- Builder: -\n- User Config: modules, $production, components, devtools, app, css, site, mdc, ui, compatibilityDate, nitro, vite, eslint, fonts, icon, linkChecker, ogImage, seo, sitemap\n- Runtime Modules: @nuxtjs/seo@3.1.0, @vueuse/nuxt@13.7.0, @nuxt/ui@3.3.2, @nuxt/eslint@1.9.0, @nuxt/scripts@0.11.10, motion-v/nuxt@1.7.0, @nuxtjs/mdc@0.17.2\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Package\n\nv3.x\n\n### Version\n\nv3.3.2\n\n### Reproduction\n\n```vue\n\u003Cscript setup lang=\"ts\">\n// This causes TypeScript error\nconst handleFileChange = (file: File | File[] | null) => {\n console.log(file);\n};\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUFileUpload @update:model-value=\"handleFileChange\" />\n\u003C/template>\n```\n\n### Description\n\nThe `@update:model-value` event handler for `UFileUpload` component emits `unknown` type instead of the documented type `File | File[] | null | undefined`.\n\n**Expected Behavior (per documentation)**\nAccording to the [official documentation](https://ui.nuxt.com/components/file-upload#emits), the `@update:model-value` event should emit:\n- `[value: File | File[] | null | undefined]`\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3206,3207,3208],{"name":3183,"color":3184},{"name":3156,"color":3157},{"name":3187,"color":3188},4852,"Type mismatch: UFileUpload @update:model-value emits unknown instead of documented type","2025-09-01T10:56:13Z","https://github.com/nuxt/ui/issues/4852",0.75653243,{"description":3215,"labels":3216,"number":3220,"owner":3143,"repository":3159,"state":3174,"title":3221,"updated_at":3222,"url":3223,"score":3224},"### 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```",[3217,3218,3219],{"name":3183,"color":3184},{"name":3156,"color":3157},{"name":3187,"color":3188},3432,"UModal and useOverlay compatibility Issue","2025-03-11T13:57:03Z","https://github.com/nuxt/ui/issues/3432",0.7578636,{"description":3226,"labels":3227,"number":3235,"owner":3143,"repository":3159,"state":3174,"title":3236,"updated_at":3237,"url":3238,"score":3239},"### Description\n\nI tried to create a generic method for the table action column, but TypeScript gives an error:\n\n```js\nimport type { Row } from '@tanstack/vue-table'\nimport UButton from '@nuxt/ui/runtime/components/Button.vue'\nimport UDropdownMenu from '@nuxt/ui/runtime/components/DropdownMenu.vue'\n\nexport const actionColumn = (row: Row\u003Cany>, getRowItems: (row: Row\u003Cany>) => any[]) => {\n return h(\n 'div',\n { class: 'text-right' },\n h(\n UDropdownMenu, // \u003C-- Error\n {\n content: {\n align: 'end'\n },\n items: getRowItems(row)\n },\n () => h(UButton, {\n icon: 'i-lucide-ellipsis-vertical',\n color: 'neutral',\n variant: 'ghost',\n class: 'ml-auto'\n })\n )\n )\n}\n```\n\nLint error:\n```\nNo overload matches this call.\n The last overload gave the following error.\n Argument of type '\u003CT extends DropdownMenuItem>(__VLS_props: NonNullable\u003CAwaited\u003Ctypeof __VLS_setup>>[\"props\"], __VLS_ctx?: __VLS_PrettifyLocal\u003CPick\u003CNonNullable\u003CAwaited\u003Ctypeof __VLS_setup>>, \"attrs\" | \"emit\" | \"slots\">>, __VLS_expose?: NonNullable\u003CAwaited\u003Ctypeof __VLS_setup>>[\"expose\"], __VLS_setup?: Promise\u003C...>) => import(\"vue\").VNo...' is not assignable to parameter of type 'string | Component\u003C{ readonly \"onUpdate:open\"?: ((payload: boolean) => any) | undefined; size?: \"sm\" | \"md\" | \"xs\" | \"lg\" | \"xl\" | undefined; items?: DropdownMenuItem[] | DropdownMenuItem[][] | undefined; ... 11 more ...; modal?: boolean | undefined; } & VNodeProps & AllowedComponentProps>'.\n Type '\u003CT extends DropdownMenuItem>(__VLS_props: NonNullable\u003CAwaited\u003Ctypeof __VLS_setup>>[\"props\"], __VLS_ctx?: __VLS_PrettifyLocal\u003CPick\u003CNonNullable\u003CAwaited\u003Ctypeof __VLS_setup>>, \"attrs\" | \"emit\" | \"slots\">>, __VLS_expose?: NonNullable\u003CAwaited\u003Ctypeof __VLS_setup>>[\"expose\"], __VLS_setup?: Promise\u003C...>) => import(\"vue\").VNo...' is not assignable to type 'FunctionalComponent\u003C{ readonly \"onUpdate:open\"?: ((payload: boolean) => any) | undefined; size?: \"sm\" | \"md\" | \"xs\" | \"lg\" | \"xl\" | undefined; items?: DropdownMenuItem[] | DropdownMenuItem[][] | undefined; ... 11 more ...; modal?: boolean | undefined; } & VNodeProps & AllowedComponentProps, {}, any, {}>'.\n Types of parameters '__VLS_ctx' and 'ctx' are incompatible.\n Type 'Omit\u003C{ attrs: Data; slots: Readonly\u003CInternalSlots>; emit: (event: string, ...args: any[]) => void; expose: \u003CExposed extends Record\u003Cstring, any> = Record\u003Cstring, any>>(exposed?: Exposed | undefined) => void; }, \"expose\">' is not assignable to type '{ emit: (evt: \"update:open\", payload: boolean) => void; slots: (Readonly\u003C{ default(props: { open: boolean; }): any; item: SlotProps\u003CDropdownMenuItem>; 'item-leading': SlotProps\u003C...>; 'item-label': SlotProps\u003C...>; 'item-trailing': SlotProps\u003C...>; } & (Record\u003C...> | (Record\u003C...> & Record\u003C...>))> & { ...; }) & (Record\u003C...'.\n Types of property 'slots' are incompatible.\n Type 'Readonly\u003CInternalSlots>' is not assignable to type '(Readonly\u003C{ default(props: { open: boolean; }): any; item: SlotProps\u003CDropdownMenuItem>; 'item-leading': SlotProps\u003CDropdownMenuItem>; 'item-label': SlotProps\u003C...>; 'item-trailing': SlotProps\u003C...>; } & (Record\u003C...> | (Record\u003C...> & Record\u003C...>))> & { ...; }) & (Record\u003C...> | (Record\u003C...> & Record\u003C...>))'.ts(2769)\n```\n\n\nAlthough there is this error, this piece of code actually works fine.\n\n\nref: https://ui3.nuxt.dev/components/table#with-row-actions\n\n\n",[3228,3229,3230,3233],{"name":3153,"color":3154},{"name":3156,"color":3157},{"name":3231,"color":3232},"closed-by-bot","ededed",{"name":3234,"color":3232},"stale",2968,"Using UDropdownMenu with H causes a TSLint error in a separate utils file","2025-09-06T02:01:03Z","https://github.com/nuxt/ui/issues/2968",0.760637,{"description":3241,"labels":3242,"number":3245,"owner":3143,"repository":3159,"state":3174,"title":3246,"updated_at":3247,"url":3248,"score":3249},"### Description\n\nAny idea how to configure a Table to support draggable rows if some of them are also extended?\n\nLooks like solution proposed in docs: https://ui.nuxt.com/components/table#with-drag-and-drop does not take into account that extended rows are just added as another `\u003Ctr>` element to `\u003Ctbody>`. \n",[3243,3244],{"name":3153,"color":3154},{"name":3156,"color":3157},4454,"Draggable table with expanded rows","2025-07-14T17:31:26Z","https://github.com/nuxt/ui/issues/4454",0.7635003,{"description":3251,"labels":3252,"number":3255,"owner":3143,"repository":3159,"state":3174,"title":3256,"updated_at":3257,"url":3258,"score":3259},"### Environment\n\nNuxt 3.15.4\nNuxt UI https://pkg.pr.new/@nuxt/ui@e7e7585\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.15.4\n\n### Reproduction\n\n-\n\n### Description\n\nJust noticed the following components work as expected in a fieldForm\n\n```\n \u003CUFormField\n v-if=\"isVisible\"\n :name=\"fieldName\"\n :label=\"field['#title']\"\n :required=\"!!field['#required']\"\n >\n \u003Ctemplate\n v-if=\"descriptionContent && field['#type'] !== 'checkbox'\"\n #description\n >\n \u003Cspan v-html=\"cleanHTML(descriptionContent)\" />\n \u003C/template>\n\n \u003Ccomponent\n v-if=\"resolvedComponent\"\n :is=\"resolvedComponent\"\n :field=\"field\"\n :fieldName=\"fieldName\"\n :state=\"state\"\n />\n\n \u003Ctemplate v-if=\"helpContent\" #help>\n \u003Cspan v-html=\"cleanHTML(helpContent)\" />\n \u003C/template>\n \u003C/UFormField>\n```\n\n ```\n \u003CURadioGroup\n v-model=\"state[fieldName]\"\n :items=\"transformOptions(field['#options'] || {})\"\n orientation=\"horizontal\"\n class=\"w-full\"\n />\n```\n\n```\n \u003CUSelect\n v-model=\"state[fieldName]\"\n placeholder=\"Select\"\n :items=\"transformOptions(field['#options'] || {})\"\n class=\"w-full\"\n />\n\n```\nHowever when using a UCheckbox label and description have to be set here\n\n```\n \u003CUCheckbox\n v-model=\"checkboxValue\"\n :label=\"field['#title']\"\n :description=\"field['#description']\"\n class=\"w-full\"\n @update:model-value=\"props.state[fieldName] = $event\"\n />\n```\n\nSeems like this is a bug or maybe this is by design?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3253,3254],{"name":3153,"color":3154},{"name":3156,"color":3157},3294,"UCheckbox fieldform support","2025-02-12T19:23:36Z","https://github.com/nuxt/ui/issues/3294",0.76614887,["Reactive",3261],{},["Set"],["ShallowReactive",3264],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fupnNLk7JcrtyvGbM0_6QVt7VdGz1JykzxsCkIo4WoDA":-1},"/nuxt/ui/3982"]