\n \u003CUButton\n @click=\"add\">Add\n \u003C/UButton>\n \u003C/div>\n\u003C/template>\n```\n\n### Description\n\nAfter click the \"add\" button, it will push a new data into dataRef, but the Table will not rendering new data\n\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2943,2944,2945],{"name":2897,"color":2898},{"name":2923,"color":2924},{"name":2886,"color":2887},3597,"UTable data updated but UI will not update","2025-03-24T02:11:33Z","https://github.com/nuxt/ui/issues/3597",0.71797687,{"description":2952,"labels":2953,"number":2956,"owner":2874,"repository":2875,"state":2926,"title":2957,"updated_at":2958,"url":2959,"score":2960},"### Description\n\nHow do I override e.g. `ui.modal.variants.fullscreen.false` styles for just one element?",[2954,2955],{"name":2868,"color":2869},{"name":2886,"color":2887},3704,"How to override variants for single components","2025-03-28T08:52:19Z","https://github.com/nuxt/ui/issues/3704",0.72798634,{"description":2962,"labels":2963,"number":2965,"owner":2874,"repository":2875,"state":2926,"title":2966,"updated_at":2967,"url":2968,"score":2969},"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'. ",[2964],{"name":2886,"color":2887},3687,"Allow specify portal destination for all portaled components","2025-04-21T15:42:56Z","https://github.com/nuxt/ui/issues/3687",0.73315024,{"description":2971,"labels":2972,"number":2978,"owner":2874,"repository":2875,"state":2926,"title":2979,"updated_at":2980,"url":2981,"score":2982},"### 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_",[2973,2976,2977],{"name":2974,"color":2975},"enhancement","a2eeef",{"name":2886,"color":2887},{"name":2901,"color":2902},3810,"[UForm] Feature Request: Make deferInputValidation Configurable in useFormField","2025-04-20T15:25:42Z","https://github.com/nuxt/ui/issues/3810",0.7371877,["Reactive",2984],{},["Set"],["ShallowReactive",2987],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f8aFtGADIeSR6Lpwm-hm3cVWf08oVOc2wmcKos1mu5ck":-1},"/nuxt/ui/3753"]