\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```",[2918,2919,2920],{"name":2868,"color":2869},{"name":2874,"color":2875},{"name":2877,"color":2878},3699,"tooltip with avatar without src do not work","2025-03-28T09:27:27Z","https://github.com/nuxt/ui/issues/3699",0.724864,{"description":2927,"labels":2928,"number":2930,"owner":2880,"repository":2881,"state":2882,"title":2931,"updated_at":2932,"url":2933,"score":2934},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v22.3.0`\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: `yarn@1.22.22`\r\n- Builder: `-`\r\n- User Config: `compatibilityDate`, `devtools`, `modules`, `plugins`, `runtimeConfig`, `i18n`\r\n- Runtime Modules: `@nuxt/ui@2.18.4`, `@nuxtjs/i18n@8.5.1`\r\n- Build Modules: `-`\r\n\n\n### Version\n\nv2.18.4\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-jfdc58?file=app.vue,app.config.ts\n\n### Description\n\n## Description\r\nThe Nuxt UI notification component is currently being created and added to the DOM even when no toast has been triggered. This behavior leads to unintended consequences due to the component's z-index:\r\n\r\nThe notification component occupies part of the screen unnecessarily.\r\nIt overlaps other elements on the page due to its z-index, potentially disrupting the user interface.\r\n\r\n## Expected Behavior\r\nThe notification component should only be created and added to the DOM when a toast is actually triggered.\r\n\r\n## Current Behavior\r\nThe notification component is always present in the DOM, regardless of whether a toast has been triggered or not.\r\n\r\n## Steps to Reproduce\r\n\r\n- Implement the Nuxt UI notification component in a project.\r\n- Inspect the DOM without triggering any toasts.\r\n- Observe that the notification component is present and has a z-index applied.\r\n\r\n## Additional Context\r\nThis issue affects the usability and performance of applications using the Nuxt UI notification component. Resolving it would improve both the user experience and the overall efficiency of the component.\r\n\r\n## Possible Solution\r\nConsider implementing a conditional rendering approach where the notification component is only added to the DOM when it's actually needed (i.e., when a toast is triggered).\r\n\u003Cimg width=\"1427\" alt=\"Screenshot 2024-09-04 at 6 29 00 PM\" src=\"https://github.com/user-attachments/assets/da90352f-71e6-4aaf-9bda-7a9e4a3fd056\">\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2929],{"name":2868,"color":2869},2113,"Notification component created even when toast is not triggered, causing z-index issues","2024-11-09T10:24:37Z","https://github.com/nuxt/ui/issues/2113",0.72976,{"description":2936,"labels":2937,"number":2939,"owner":2880,"repository":2880,"state":2882,"title":2940,"updated_at":2941,"url":2942,"score":2943},"\r\n",[2938],{"name":2900,"color":2901},15558,"Typo in codebase: `transfrom` instead of `transform`","2023-01-19T17:54:13Z","https://github.com/nuxt/nuxt/issues/15558",0.7357851,{"description":2945,"labels":2946,"number":2952,"owner":2880,"repository":2881,"state":2882,"title":2953,"updated_at":2954,"url":2955,"score":2956},"### 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_",[2947,2950,2951],{"name":2948,"color":2949},"enhancement","a2eeef",{"name":2874,"color":2875},{"name":2877,"color":2878},3810,"[UForm] Feature Request: Make deferInputValidation Configurable in useFormField","2025-04-20T15:25:42Z","https://github.com/nuxt/ui/issues/3810",0.73780304,{"description":2958,"labels":2959,"number":2960,"owner":2880,"repository":2961,"state":2882,"title":2962,"updated_at":2963,"url":2964,"score":2965},"\r\n",[],28,"icon","ts error ","2022-12-19T15:51:38Z","https://github.com/nuxt/icon/issues/28",0.7415233,{"description":2967,"labels":2968,"number":2974,"owner":2880,"repository":2881,"state":2882,"title":2975,"updated_at":2976,"url":2977,"score":2978},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v22.13.0\n- Nuxt Version: 3.16.0\n- CLI Version: 3.23.0\n- Nitro Version: 2.11.6\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: devtools, modules, css, future, compatibilityDate, runtimeConfig\n- Runtime Modules: @nuxt/ui@3.0.0, @nuxt/eslint@1.2.0, nuxt-echarts@0.2.6\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0\n\n### Reproduction\n\n```vue\n\u003Cscript setup lang=\"ts\">\nconst data = ref([\n {\n id: '0',\n },\n])\n\nconst add = () => {\n data.value.push({\n id: `${data.value.length}`,\n })\n console.log(data.value)\n}\n\n\u003C/script>\n\n\u003Ctemplate>\n \u003Cdiv>\n \u003CUTable :data=\"data\" class=\"flex-1\"/>\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```",[2969,2970,2973],{"name":2868,"color":2869},{"name":2971,"color":2972},"duplicate","cfd3d7",{"name":2874,"color":2875},3597,"UTable data updated but UI will not update","2025-03-24T02:11:33Z","https://github.com/nuxt/ui/issues/3597",0.75225484,["Reactive",2980],{},["Set"],["ShallowReactive",2983],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f458l1P2eZcA2Korg0NQuQ5qKPLatKGMUTgqbIuNSR_s":-1},"/nuxt/ui/2241"]