\n \u003C/UButton>\n\n \u003CUButton color=\"gray\" variant=\"ghost\" @click=\"continue\">\n Continue\n \u003CUIcon name=\"i-mdi-arrow-right-circle\" class=\"text-primary\" />\n \u003C/UButton>\n \u003C/div>\n \u003C/UCard>\n \u003C/UModal>\n```",[2001,2004],{"name":2002,"color":2003},"question","d876e3",{"name":2005,"color":2006},"stale","ededed",3187,"[V2] How to prevent button pre-selection on UModal?","2025-03-09T01:50:32Z","https://github.com/nuxt/ui/issues/3187",0.7378104,{"description":2013,"labels":2014,"number":2022,"owner":1991,"repository":1992,"state":1993,"title":2023,"updated_at":2024,"url":2025,"score":2026},"### Description\n\nThe PinInput component expects the v-model to be a string array. However, when the type is set to number, I think it should support an array of numbers as values too.\n\n### Additional context\n\n_No response_",[2015,2018,2021],{"name":2016,"color":2017},"enhancement","a2eeef",{"name":2019,"color":2020},"v3","49DCB8",{"name":1988,"color":1989},3751,"PinInput: v-model support Number-Array on type=number","2025-03-31T10:31:31Z","https://github.com/nuxt/ui/issues/3751",0.7477712,{"description":2028,"labels":2029,"number":2032,"owner":1991,"repository":1992,"state":1993,"title":2033,"updated_at":2034,"url":2035,"score":2036},"I currently have the problem that we have to integrate our SPA into a larger application. And with that, we also inherit the CSS of the outer application. And that's where it gets really ugly: they have partially written classes in their own CSS files that use the TW naming scheme (m, p, gap, shadow, etc.), and then add `!important` to these declarations. \n\nOne of the big problems with Nuxt UI is that there is no prefixing of Tailwind classes. So we started writing TW utilities with a prefix for the affected classes. This is then transferred to app.config. The second problem was the merge process that app.config uses. Usually the names have to match. If I want to have a `p-4` from the config (because px values with !important were entered in the outer CSS), I created the class `p-00`, which replaces the `p-4` class and thus clears the way for the prefixed TW class `o-p-4`.\n\nSo far so good, but I can't use it with popovers like SelectMenu. No matter what I do, the class `shadow-lg` remains. The other devs of the main application have entered a rather ugly shadow with important there. \n\nIs there another prop like 'content' that I can use to replace `shadow-lg`? I'm not a fan of `!important`, but at this point I can only work this way.\n\nFurthermore, it would be really nice if you could really overwrite the sections in app.config instead of just merging them (apart from prefixing the TW classes). There are certain stylings that you won't use, but then they are in the element",[2030,2031],{"name":2002,"color":2003},{"name":2019,"color":2020},3874,"Changing Shadow Classes on Popover and SelectMenu","2025-04-13T13:53:28Z","https://github.com/nuxt/ui/issues/3874",0.7528997,{"description":2038,"labels":2039,"number":2043,"owner":1991,"repository":1992,"state":1993,"title":2044,"updated_at":2045,"url":2046,"score":2047},"### 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_",[2040,2041,2042],{"name":2016,"color":2017},{"name":2019,"color":2020},{"name":1988,"color":1989},3810,"[UForm] Feature Request: Make deferInputValidation Configurable in useFormField","2025-04-06T16:27:47Z","https://github.com/nuxt/ui/issues/3810",0.75603807,{"description":2049,"labels":2050,"number":2053,"owner":1991,"repository":1992,"state":2054,"title":2055,"updated_at":2056,"url":2057,"score":2058},"### 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```",[2051,2052],{"name":1985,"color":1986},{"name":2019,"color":2020},2649,"closed","breadcrumb HTML validation errors","2024-11-15T08:53:33Z","https://github.com/nuxt/ui/issues/2649",0.69771254,{"description":2060,"labels":2061,"number":2066,"owner":1991,"repository":1992,"state":2054,"title":2067,"updated_at":2068,"url":2069,"score":2070},"### Environment\n\n- Operating System: Darwin\r\n- Node Version: v18.18.2\r\n- Nuxt Version: 3.13.1\r\n- CLI Version: 3.13.1\r\n- Nitro Version: 2.9.7\r\n- Package Manager: bun@1.1.24\r\n- Builder: -\r\n- User Config: devtools, modules, eslint, runtimeConfig, site, mdc, image, components, strapi, i18n, vite, routeRules, formkit, compatibilityDate\r\n- Runtime Modules: @nuxtjs/strapi@1.12.0, @nuxt/image@1.8.0, @vueuse/nuxt@10.11.1, @nuxtjs/i18n@8.5.1, @nuxt/eslint@0.3.13, @nuxt/fonts@0.7.2, @nuxtjs/mdc@0.8.3, @formkit/nuxt@1.6.5, nuxt3-vuex-module@1.1.0, nuxt3-interpolation/index.cjs, nuxt-swiper@1.2.2, nuxt-marquee@1.0.4, @nuxtjs/seo@2.0.0-rc.20, @formkit/nuxt@1.6.5, @nuxt/ui@2.18.4\r\n- Build Modules: -\n\n### Version\n\nv2.18.4\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-dbk9vy?file=app.vue\n\n### Description\n\nEnter transition of sliderover Module not working properly. Instant appearing of elements (with sometimes slight but too quick transitions). Exit transition works fine. \r\n\r\nTried on Chrome, Firefox & Safari on Mac.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2062,2063],{"name":1985,"color":1986},{"name":2064,"color":2065},"upstream","78bddb",2127,"[Slideover/Modal] Enter transition not working","2024-09-20T14:03:47Z","https://github.com/nuxt/ui/issues/2127",0.7087463,{"description":2072,"labels":2073,"number":2076,"owner":1991,"repository":1992,"state":2054,"title":2077,"updated_at":2078,"url":2079,"score":2080},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v20.10.0\n- Nuxt Version: 3.15.0\n- CLI Version: 3.17.2\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.15.1\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.9, @nuxt/eslint@0.7.4\n- Build Modules: -\n------------------------------\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.0-alpha.10\n\n### Reproduction\n\nRepo: https://github.com/Cyanhall/nuxt-ui-v3-demo/tree/main/demo3\n\nCode: https://github.com/Cyanhall/nuxt-ui-v3-demo/blob/main/demo3/app/components/SearchPalette.vue#L46\n\n### Description\n\nThe placeholder in UInput within UModal does not display.\n\n```vue\n\u003CUInput\n class=\"w-full mb-4\"\n size=\"sm\"\n icon=\"i-lucide-search\"\n placeholder=\"Search...\"\n>\n \u003Ctemplate #trailing>\n \u003CUKbd value=\"shift\" />\n \u003CUKbd value=\"G\" />\n \u003C/template>\n\u003C/UInput>\n```\n\u003Cimg width=\"496\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/be2e8457-b3ac-4b70-838b-2b2b7399c091\" />\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2074,2075],{"name":1985,"color":1986},{"name":2019,"color":2020},2977,"The placeholder in UInput within UModal does not display","2025-03-03T09:06:21Z","https://github.com/nuxt/ui/issues/2977",0.72863525,{"description":2082,"labels":2083,"number":2084,"owner":1991,"repository":2085,"state":2054,"title":2086,"updated_at":2087,"url":2088,"score":2089},"### Environment\n\n- All current versions of Chrome, Firefox, and Edge\n\n### Reproduction\n\n1. Go to the [introduction page](https://nuxt.com/docs/getting-started/introduction)\r\n2. Click on any other page on the left sidebar\r\n3. Click on any section in the right table of contents\r\n4. Go back to the introduction page\r\n\r\n\r\n\n\n### Describe the bug\n\nNo idea what's going on since the Docs repo isn't available yet.\r\n\r\nIn Firefox this throws `\"TypeError: e.value is null\"` while on Chrome/Edge it's `\"TypeError: Cannot read properties of null (reading 'querySelectorAll')\"`\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[],1224,"nuxt.com","[Docs] introduction page throws an error after navigation","2023-10-10T14:45:11Z","https://github.com/nuxt/nuxt.com/issues/1224",0.7308376,{"description":2091,"labels":2092,"number":2093,"owner":1991,"repository":2085,"state":2054,"title":2094,"updated_at":2095,"url":2096,"score":2097},"- [x] Colors & Fonts\n- [x] Landing page (Home)\n- [x] Showcase categories/hero\n- [x] Modules categories/hero\n- [x] Blog categories/hero\n- [x] Support hero/content",[],1305,"Marketing Update","2023-07-04T10:00:31Z","https://github.com/nuxt/nuxt.com/issues/1305",0.7347363,["Reactive",2099],{},["Set"],["ShallowReactive",2102],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"Znz4qXsL8zfqqhnSmTqgg7jEEjR5l0DAYJQU4WoB8LE":-1},"/nuxt/ui/2573"]