`\nThis props was available on Nuxt UI V2.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3020,3023,3026],{"name":3021,"color":3022},"bug","d73a4a",{"name":3024,"color":3025},"v3","49DCB8",{"name":3027,"color":3028},"triage","ffffff",3703,"nuxt","ui","closed","Missing Container UI props","2025-03-27T09:43:56Z","https://github.com/nuxt/ui/issues/3703",0.6574489,{"description":3038,"labels":3039,"number":3044,"owner":3030,"repository":3031,"state":3032,"title":3045,"updated_at":3046,"url":3047,"score":3048},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.x\n\n### Description\n\nI would like the `useModal` composable to supports opening multiple modals.\n\n### Additional context\n\n_No response_",[3040,3043],{"name":3041,"color":3042},"enhancement","a2eeef",{"name":3024,"color":3025},2799,"[v3][UModal] `useModal` supports multiple modals at the same time","2025-02-27T16:32:50Z","https://github.com/nuxt/ui/issues/2799",0.68140996,{"description":3050,"labels":3051,"number":3054,"owner":3030,"repository":3055,"state":3032,"title":3056,"updated_at":3057,"url":3058,"score":3059},"\n",[3052],{"name":3021,"color":3053},"ff281a",465,"nuxt.com","[Milkdown] Can't put a cursor between components","2022-06-15T12:48:21Z","https://github.com/nuxt/nuxt.com/issues/465",0.7298395,{"description":3061,"labels":3062,"number":3066,"owner":3030,"repository":3031,"state":3032,"title":3067,"updated_at":3068,"url":3069,"score":3070},"### For what version of Nuxt UI are you asking this question?\n\nv2.x\n\n### Description\n\nHello, first of all thank you for your fairly complete UI modules! \n\nI'm trying to do multi-line with the slot option of your UTooltip component, unfortunately it only displays the first line. \n\nIs it possible to do this ? Do you have a use case to show me please ?\n\nThank you in advance !",[3063],{"name":3064,"color":3065},"question","d876e3",2530,"Multi-line of UTooltip Component","2024-11-06T16:43:15Z","https://github.com/nuxt/ui/issues/2530",0.73190045,{"description":3072,"labels":3073,"number":3077,"owner":3030,"repository":3031,"state":3032,"title":3078,"updated_at":3079,"url":3080,"score":3081},"### Environment\n\nOS Linux\nnode v22.14\n\nnuxt v3.16.1\nnuxt ui v3.0.1\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.16.1\n\n### Reproduction\n\n\nhttps://codesandbox.io/p/devbox/peaceful-newton-7rrnpq?workspaceId=ws_BXPvVpCjQQH8Dp7pSA8M1q\n\n### Description\n\nA tooltip with, as content, an Avatar without src prop did not display the popup.\n\n ```\n\u003CUTooltip arrow text=\"title\">\n \u003CUAvatar text=\"Avatar\" size=\"3xl\" />\n \u003C/UTooltip>\n```\nThe popup with 'title' is never displayed\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3074,3075,3076],{"name":3021,"color":3022},{"name":3024,"color":3025},{"name":3027,"color":3028},3699,"tooltip with avatar without src do not work","2025-03-28T09:27:27Z","https://github.com/nuxt/ui/issues/3699",0.7391506,{"description":3083,"labels":3084,"number":3085,"owner":3030,"repository":3086,"state":3032,"title":3087,"updated_at":3088,"url":3089,"score":3090},"When updating from 3.0.0.rc9 to 3.3.1 I see this error:\r\n\r\n```\r\n ERROR TypeError: filters.some is not a function 16:18:54\r\n\r\n ❯ node_modules/vitest/dist/chunk-vite-node-externalize.6956d2d9.mjs:10719:51 16:18:54\r\n ❯ Vitest.globTestFiles node_modules/vitest/dist/chunk-vite-node-externalize.6956d2d9.mjs:10719:29 16:18:54\r\n ❯ process.processTicksAndRejections node:internal/process/task_queues:95:5 16:18:54\r\n ❯ Vitest.start node_modules/vitest/dist/chunk-vite-node-externalize.6956d2d9.mjs:10472:50 16:18:54\r\n ❯ startVitest node_modules/vitest/dist/chunk-vite-node-externalize.6956d2d9.mjs:11204:5 16:18:54\r\n ❯ runTests node_modules/@nuxt/test-utils/dist/index.mjs:311:21 16:18:54\r\n ❯ Object.invoke node_modules/nuxi/dist/chunks/test.mjs:14:5 16:18:54\r\n ❯ _main node_modules/nuxi/dist/cli.mjs:49:20 \r\n```",[],418,"test-utils","TypeError: filters.some is not a function ","2023-12-02T00:13:09Z","https://github.com/nuxt/test-utils/issues/418",0.74478024,{"description":3092,"labels":3093,"number":3095,"owner":3030,"repository":3031,"state":3032,"title":3096,"updated_at":3097,"url":3098,"score":3099},"Currently, portal components (modals, popovers, etc.) are directly attached to the root of the body. It would be beneficial to allow specifying their destination within the configuration .This would provide greater control over rendering order and potential styling conflicts, especially in complex applications with open shadow Dom. \n\nFor instance, a developer might want to render a modal within a specific container to inherit styles or avoid interference with other elements on the page (I currently using Nuxt ui as a web component withing WordPress). \n\nThe proposed configuration option could be a CSS selector string, allowing for flexible targeting of any existing element in the DOM defaulting to 'body'. ",[3094],{"name":3024,"color":3025},3687,"Allow specify portal destination for all portaled components","2025-04-21T15:42:56Z","https://github.com/nuxt/ui/issues/3687",0.7541379,{"description":3101,"labels":3102,"number":3105,"owner":3030,"repository":3031,"state":3032,"title":3106,"updated_at":3107,"url":3108,"score":3109},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v20.11.1\n- Nuxt Version: 3.14.159\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.11.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.8, @nuxtjs/html-validator@1.8.2, @nuxt/image@1.8.1, @nuxt/eslint@0.6.1, @nuxtjs/seo@2.0.0-rc.23\n- Build Modules: -\n------------------------------\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n\"@nuxt/ui\": \"3.0.0-alpha.8\",\n\n### Reproduction\n\n\u003C!-- layouts/default.vue -->\n\u003Ctemplate>\n \u003Cdiv class=\"container mx-auto\">\n \u003Cu-breadcrumb :items=\"items \" />\n \u003Cslot>\u003C/slot>\n \u003C/div>\n\u003C/template>\n\n\n\u003Cscript lang=\"ts\" setup>\nimport { useRoute } from 'vue-router';\n\nconst route = useRoute();\nconst items = useBreadcrumbItems({\n schemaOrg: true,\n});\n\u003C/script>\n\n\n### Description\n\nthis will render the breadcrumbs in a \u003Cdiv> with an aria-label, which is a violation of this rule: https://html-validate.org/rules/aria-label-misuse.html\n\n- Rule ID: aria-label-misuse\n- Category: Accessibility\n- Standards: WCAG 2.2 (A)WCAG 2.1 (A)WCAG 2.0 (A)\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n ERROR HTML validation errors found for /song/justice-genesis-1\n\ninline\n 129:21990 error \"aria-label\" cannot be used on this element aria-label-misuse\n\n✖ 1 problem (1 error, 0 warnings)\n\nMore information:\n https://html-validate.org/rules/aria-label-misuse.html\n\n```",[3103,3104],{"name":3021,"color":3022},{"name":3024,"color":3025},2649,"breadcrumb HTML validation errors","2024-11-15T08:53:33Z","https://github.com/nuxt/ui/issues/2649",0.76639086,{"description":3111,"labels":3112,"number":3115,"owner":3030,"repository":3031,"state":3032,"title":3116,"updated_at":3117,"url":3118,"score":3119},"### Environment\n\nOperating System: `Darwin`\nNode Version: `v22.11.0`\nNuxt Version: `3.14.1592`\nCLI Version: `3.16.0`\nNitro Version: `2.10.4`\nPackage Manager: `npm@10.9.0`\nBuilder: -\nUser Config: `default`\nRuntime Modules: `@nuxt/ui@3.0.0-alpha.9, @nuxt/eslint@0.7.2, @nuxt/image@1.8.1`\nBuild Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.9\n\n### Reproduction\n\nhttps://github.com/makvv4/nuxtui3-avatar-bug-reproduction\n\n### Description\n\nIn the markup we see the correct link to the image, but in the avatar component only a fallback is displayed.\nIn the Network tab, you can see that there are multiple requests made at the same time: one with the correct link, and another request links to the localhost.\n\nThe provider is located in `/providers/my-img-provider.ts`\nAnd config looks like:\n```javascript\nexport default defineNuxtConfig({\n devtools: { enabled: true },\n modules: ['@nuxt/ui', '@nuxt/eslint', '@nuxt/image'],\n css: ['~/assets/css/main.css'],\n\n future: {\n compatibilityVersion: 4,\n },\n\n compatibilityDate: '2024-11-27',\n\n image: {\n providers: {\n myImgProvider: {\n provider: '~~/providers/my-img-provider.ts',\n },\n },\n provider: 'myImgProvider',\n },\n})\n```\n\n### Additional context\n\n\n\n\n\n\n\n\n\n### Logs\n\n```shell-script\n\n```",[3113,3114],{"name":3021,"color":3022},{"name":3024,"color":3025},2857,"[v3][UAvatar] `UAvatar` breaks when using `@nuxt/image` with custom provider","2025-01-11T15:14:06Z","https://github.com/nuxt/ui/issues/2857",0.7666423,{"description":3121,"labels":3122,"number":3126,"owner":3030,"repository":3031,"state":3032,"title":3127,"updated_at":3128,"url":3129,"score":3130},"### Description\n\n\n## 🔧 Current Behavior\n\nThe `deferInputValidation` parameter in `useFormField` is currently hardcoded in the `Input` component:\n\n```ts\nconst { emitFormBlur, emitFormInput, /* ... */ } = useFormField\u003CInputProps>(props, { \n deferInputValidation: false // Hardcoded\n})\n```\n\nThis limits flexibility, as consumers of the `Input` component cannot control validation timing behavior (e.g., validate on blur vs. validate on input).\n\n## ✅ Proposed Solution\n\nMake `deferInputValidation` configurable via a component prop:\n\n1. **Pass dynamic value to `useFormField`:**\n\n```ts\nuseFormField\u003CInputProps>(props, {\n deferInputValidation: props.deferInputValidation\n})\n```\n\n2. **Update the component props interface:**\n\n```ts\ndeferInputValidation?: boolean\n```\n\n---\n\n## 💡 Use Cases\n\n- **Delayed validation** for complex, interdependent form fields \n- **Immediate validation** for sensitive or critical fields \n- Flexibility for UX patterns like **\"validate-on-blur\"** or **\"validate-as-you-type\"**\n\n---\n\n## 🔁 Alternatives Considered\n\n- **Wrapper Component**: Adds unnecessary complexity \n- **Global Form-Level Config**: Less flexible than per-field control\n\n---\n\n## 🧪 Testing Impact\n\n- Covered by existing validation tests with both `true` and `false` cases\n\n---\n\n## 📚 Documentation\n\nRequires updates to:\n\n- Component prop API \n- Form validation best practices\n\n---\n\n## ⚙️ Why This Matters\n\nThis change supports **Inversion of Control** — empowering component consumers to control validation timing based on specific UX needs.\n```\n\n### Additional context\n\n_No response_",[3123,3124,3125],{"name":3041,"color":3042},{"name":3024,"color":3025},{"name":3027,"color":3028},3810,"[UForm] Feature Request: Make deferInputValidation Configurable in useFormField","2025-04-20T15:25:42Z","https://github.com/nuxt/ui/issues/3810",0.76827997,["Reactive",3132],{},["Set"],["ShallowReactive",3135],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fhu2XmZ29b2kewyxVpP_lZxKQJ9zCRjSKLtT-3fRSxWs":-1},"/nuxt/ui/3459"]