\n \u003C/slot> \n```\n\n### Additional context\n\nI believe this is common throughout the library, and was wondering to post this issue or not given that there might already be a specific reason. But alas, I couldn't find one in the issues.\n\ncc, from #4411",[2907,2910,2913],{"name":2908,"color":2909},"enhancement","a2eeef",{"name":2911,"color":2912},"v3","49DCB8",{"name":2914,"color":2915},"triage","ffffff",4435,"nuxt","ui","open","InputNumber increment/decrement button props not being passed to their respective slots","2025-07-01T17:13:20Z","https://github.com/nuxt/ui/issues/4435",0.73485446,{"description":2925,"labels":2926,"number":2932,"owner":2917,"repository":2918,"state":2919,"title":2933,"updated_at":2934,"url":2935,"score":2936},"### Environment\n\n- Operating System: `Windows_NT`\n- Node Version: `v22.14.0`\n- Nuxt Version: `3.17.5`\n- CLI Version: `3.25.1`\n- Nitro Version: `2.11.12`\n- Package Manager: `npm@10.9.2`\n- Builder: `-`\n- User Config: `compatibilityDate`, `devtools`, `srcDir`, `routeRules`, `app`, `svgSprite`, `alias`, `css`, `imports`, `modules`, `ssr`, `runtimeConfig`\n- Runtime Modules: `@nuxt/eslint@1.4.1`, `@nuxt/fonts@0.11.4`, `@nuxt/icon@1.14.0`, `@nuxt/image@1.10.0`, `@nuxt/scripts@0.11.8`, `@nuxt/test-utils@3.19.1`, `@nuxt/ui@3.1.3`, `@nuxtjs/svg-sprite@1.0.2`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.2.0\n\n\n### Description\n\n\n\nHi when i select copy payment id i got that error when i console log the row it gives me undefined upon clicking kindly check this link: https://ui.nuxt.com/components/table#with-context-menu\n\n#4259 \n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2927,2930,2931],{"name":2928,"color":2929},"bug","d73a4a",{"name":2911,"color":2912},{"name":2914,"color":2915},4452,"UTable context menu error during selection of items","2025-07-03T03:34:35Z","https://github.com/nuxt/ui/issues/4452",0.7395233,{"description":2938,"labels":2939,"number":2943,"owner":2917,"repository":2918,"state":2919,"title":2944,"updated_at":2945,"url":2946,"score":2947},"### Environment\n\n```\n Operating System: Linux\n Node Version: v18.19.1\n Nuxt Version: 3.16.0\n CLI Version: 3.23.0\n Nitro Version: 2.11.6\n Package Manager: npm@10.2.4\n Builder: -\n User Config: compatibilityDate, devtools, colorMode, modules, css, i18n, runtimeConfig\n Runtime Modules: @nuxt/eslint@1.2.0, @nuxt/ui@3.1.3, @nuxt/test-utils@3.17.2, @nuxt/icon@1.13.0, @nuxtjs/i18n@9.3.1 @pinia/nuxt@0.10.1, @nuxt/image@1.10.0\n Build Modules: -\n```\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.16.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/goofy-yalow-xftq2n\n\n### Description\n\nI've set value of `--ui-text-dimmed` to red. If I use `text-dimmed` on paragraph its text color is red. However input's placeholder color is not affected (even though it has placeholder:text-dimmed class by default)\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2940,2941,2942],{"name":2928,"color":2929},{"name":2911,"color":2912},{"name":2914,"color":2915},4301,"Input's placeholder doesn't respect value of `--ui-text-dimmed`","2025-06-06T09:22:24Z","https://github.com/nuxt/ui/issues/4301",0.7501471,{"description":2949,"labels":2950,"number":2954,"owner":2917,"repository":2955,"state":2919,"title":2956,"updated_at":2957,"url":2958,"score":2959},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.15.0`\n- Nuxt Version: `3.17.4`\n- CLI Version: `3.25.1`\n- Nitro Version: `2.11.12`\n- Package Manager: `yarn@1.22.19`\n- Builder: `-`\n- User Config: `compatibilityDate`, `devtools`, `modules`\n- Runtime Modules: `@nuxt/test-utils@3.19.1`\n- Build Modules: `-`\n\n\n### Reproduction\n\nhttps://github.com/cjpearson/test-utils-issue\n\n### Describe the bug\n\nAfter upgrading to Vue 3.5.15, we have a test where the component is improperly rendered. This is the output of `renderSuspended().html()`\n\n**Before (3.5.14):**\n\n```html\n\u003Cdiv id=\"test-wrapper\">\n \u003Cdiv>\n \u003Ctransition-stub appear=\"false\" persisted=\"false\" css=\"true\">\n \u003Cdialog open=\"\">\u003Cbutton data-testid=\"close-button\"> Close \u003C/button>\n \u003Cdiv>\n \u003Cdiv data-testid=\"dialog-content\"> I am some modal content \u003C/div>\n \u003C/div>\n \u003C/dialog>\n \u003C/transition-stub>\u003Cbutton data-testid=\"btn\">Open\u003C/button>\n \u003C/div>\n\u003C/div>\n```\n\n**After (3.5.15):**\n\n```html\n\u003Cdiv id=\"test-wrapper\">\n \u003Cdiv>\n \u003C!--[object Object]-->\u003Cbutton data-testid=\"btn\">Open\u003C/button>\n \u003C/div>\n\u003C/div>\n```\n\nWhile it's caused by a vue upgrade, I think this may be an issue within the test-utils because when running the application itself, everything seems to work ok.\n\n### Additional context\n\nThere seem to be a couple necessary aspects for this bug to occur:\n\n* There's a component which has a prop of type `Component`\n* The default value for this prop is imported through a barrel file\n\nI've tried narrowing down the changes in Vue 3.5.15 and it looks like [this change](https://github.com/vuejs/core/pull/13245/files) in compiler-sfc is the root cause. \n\n### Logs\n\n```shell-script\n\n```",[2951],{"name":2952,"color":2953},"pending triage","5D08F5",1312,"test-utils","Incorrect rendering with vue 3.5.15 and component props","2025-06-02T13:37:43Z","https://github.com/nuxt/test-utils/issues/1312",0.75302875,{"description":2961,"labels":2962,"number":2972,"owner":2917,"repository":2918,"state":2973,"title":2974,"updated_at":2975,"url":2976,"score":2977},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.4.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.16.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.14.4\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.9, nuxt-auth-sanctum@0.5.2, @vueuse/nuxt@11.3.0, nuxt-file-storage@0.2.9\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.14.1592\n\n### Reproduction\n\n```vue\n\u003Cscript setup lang=\"ts\">\nconst bill = defineModel()\nconst calcStep = (value: int): int => value \u003C 1000 ? 100 : 500\n\u003C/script>\n\n\u003Ctemplate>\n \u003Cdiv class=\"flex gap-4 items-center\">\n от \u003CUInputNumber v-model=\"bill.from\" :min=\"0\" :max=\"bill.to || 10000\" :step=\"calcStep(bill.from)\" variant=\"soft\" class=\"max-w-32\" />\n до \u003CUInputNumber v-model=\"bill.to\" :min=\"bill.from\" :max=\"10000\" :step=\"calcStep(bill.to)\" variant=\"soft\" class=\"max-w-32\" />\n \u003C/div>\n\u003C/template>\n```\n\n### Description\n\nhttps://skr.sh/vT5m5gCX1Bk\n\nThe value changes when clicking outside the field, regardless of the `step` and `modelValue` state. The `step` parameter is also calculated incorrectly at the threshold of 1000.",[2963,2964,2967,2968,2969],{"name":2928,"color":2929},{"name":2965,"color":2966},"needs reproduction","CB47CF",{"name":2911,"color":2912},{"name":2914,"color":2915},{"name":2970,"color":2971},"closed-by-bot","ededed",2859,"closed","UInputNumber changes value on blur when not asked for","2025-06-19T02:15:22Z","https://github.com/nuxt/ui/issues/2859",0.6374544,{"description":2979,"labels":2980,"number":2983,"owner":2917,"repository":2918,"state":2973,"title":2984,"updated_at":2985,"url":2986,"score":2987},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.19.1\n- Nuxt Version: 3.17.5\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: pnpm@8.15.6\n- Builder: -\n- User Config: modules, css, future, compatibilityDate, vite\n- Runtime Modules: @nuxt/ui@3.1.3\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.3\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-bsi7gjhw?file=app%2Fapp.vue\n\n### Description\n\nThe UInput component behaves the same way whether using `v-model` or just `:modelValue`—it retains input values when typed into. However, this is incorrect because I did not set up the `@update:modelValue` event\n\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2981,2982],{"name":2928,"color":2929},{"name":2911,"color":2912},4355,"The UInput component is not a controlled component","2025-06-16T10:45:31Z","https://github.com/nuxt/ui/issues/4355",0.69703627,{"description":2989,"labels":2990,"number":2996,"owner":2917,"repository":2918,"state":2973,"title":2997,"updated_at":2998,"url":2999,"score":3000},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.15.0\n- Nuxt Version: 3.14.159\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.13.2\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/eslint@0.4.0, @vueuse/nuxt@10.11.1, @nuxt/ui@2.19.2, @pinia/nuxt@0.5.5, nuxt-echarts@0.2.4\n- Build Modules: -\n\n### Version\n\nv2.18.4\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-8d9s2j?file=app.vue\n\n### Description\n\nThe UInput component does not handle compositionstart and compositionend events, resulting in issues for languages that rely on input composition, such as Chinese (e.g., Pinyin input). Vue’s default behavior for v-model on native input elements ensures that updates are delayed until the composition ends, preventing intermediate values from triggering updates. However, the UInput component currently lacks this mechanism, causing inconsistencies with Vue’s default form handling and leading to unexpected behavior during text composition.\n\n### Additional context\n\n\n\n```vue\n\u003Ctemplate>\n\t\u003Cinput v-model=\"keyword\" />\n\u003C/template>\n\n\u003Cscript setup>\n\tconst keyword = ref('');\n\n\twatchEffect(() => {\n\t\tconsole.log('🚀 ~ watchEffect ~ keyword.value:', keyword.value);\n\t});\n\u003C/script>\n```\n\n\n\n```vue\n\u003Ctemplate>\n\t\u003CUInput v-model=\"keyword\" />\n\u003C/template>\n\n\u003Cscript setup>\n\tconst keyword = ref('');\n\n\twatchEffect(() => {\n\t\tconsole.log('🚀 ~ watchEffect ~ keyword.value:', keyword.value);\n\t});\n\u003C/script>\n```\n\n### Logs\n\n```shell-script\n\n```",[2991,2992,2993,2994],{"name":2928,"color":2929},{"name":2914,"color":2915},{"name":2970,"color":2971},{"name":2995,"color":2971},"stale",2713,"UInput Component Lacks Proper Handling of compositionstart and compositionend","2025-06-18T09:05:41Z","https://github.com/nuxt/ui/issues/2713",0.72233045,{"description":3002,"labels":3003,"number":1226,"owner":2917,"repository":2917,"state":2973,"title":3010,"updated_at":3011,"url":3012,"score":3013},"Nuxt has some difficulties since the update of vue@2.0.6, I'm looking into it.\r\n\r\nIt's due of a change in https://github.com/vuejs/vue/commit/cb4854a50e7a44f52f54dd4707b356e3b8bf0def#diff-b92dd5290072b5c2c54f2515cc1ab572R21",[3004,3007],{"name":3005,"color":3006},"3.x","29bc7f",{"name":3008,"color":3009},"2.x","d4c5f9","Issue with vue@2.0.6 and above","2023-01-19T14:23:46Z","https://github.com/nuxt/nuxt/issues/6",0.7346822,{"description":3015,"labels":3016,"number":3022,"owner":2917,"repository":2918,"state":2973,"title":3023,"updated_at":3024,"url":3025,"score":3026},"### Environment\n\n- **Nuxt:** 3.20.0\n- **Nuxt UI:** 3.0.0-alpha.10\n- **Node.js:** v22.10.0\n- **Browser:** Chrome 132.0.6834.83\n- **OS:** macOS 14.5(23F79)\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.10\n\n### Reproduction\n\n```\n\u003Cscript setup lang=\"ts\">\nimport { range } from 'lodash';\nimport { ref } from 'vue';\n\nconst value = ref(range(100)); // 100 sliders\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUSlider v-model=\"value\" />\n\u003C/template>\n```\n\n### Description\n\nWhen using the `USlider` component to render more than 100 `SliderThumbs`, the following error occurs:\n\n```\nUncaught (in promise) Maximum recursive updates exceeded in component \u003CSliderThumb>.\n```\n\nThis error seems to happen due to recursive reactive updates when the number of slider thumbs exceeds a certain limit.\n\n**Steps to Reproduce:**\n\n1. Create a Nuxt 3 project.\n2. Install Nuxt UI 3.\n3. Add the following code to a component:\n\n```vue\n\u003Cscript setup lang=\"ts\">\nimport { range } from 'lodash';\nimport { ref } from 'vue';\n\nconst value = ref(range(100)); // 100 sliders\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUSlider v-model=\"value\" />\n\u003C/template>\n```\n\n4. Run the project and attempt to render the component.\n\n**Expected Result:**\nThe `USlider` component should render more than 100 `SliderThumbs` without any errors.\n\n**Actual Result:**\nThe following error is shown in the browser console, and the application fails to work properly:\n\n```\nUncaught (in promise) Maximum recursive updates exceeded in component \u003CSliderThumb>.\n```\n\n### Additional context\n\n- This issue seems to be caused by recursive reactive updates within the `USlider` component.\n- No documented limitations regarding the number of `SliderThumbs` were found in the Nuxt UI 3 documentation.\n\n### Logs\n\n```shell-script\n\n```",[3017,3018,3019,3020,3021],{"name":2928,"color":2929},{"name":2911,"color":2912},{"name":2914,"color":2915},{"name":2970,"color":2971},{"name":2995,"color":2971},3174,"`USlider`: Maximum recursive updates exceeded with more than 100 SliderThumbs","2025-06-18T09:02:27Z","https://github.com/nuxt/ui/issues/3174",0.73573625,{"description":3028,"labels":3029,"number":3033,"owner":2917,"repository":2918,"state":2973,"title":3034,"updated_at":3035,"url":3036,"score":3037},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v24.0.2\n- Nuxt Version: 3.17.4\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: bun@1.2.14\n- Builder: -\n- User Config: compatibilityDate, devtools, future, modules, css, runtimeConfig\n- Runtime Modules: @nuxt/ui-pro@3.1.3, @nuxtjs/supabase@1.5.1, @nuxt/image@1.10.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.3\n\n### Reproduction\n\nNo need for reproduction.\n\n### Description\n\nHi, and thanks for this amazing UI library.\nI was wondering why to use a v-model for UProgress since it does not update the script from the dom?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3030,3031,3032],{"name":2928,"color":2929},{"name":2911,"color":2912},{"name":2914,"color":2915},4232,"[UProgress]: replace v-model with :value?","2025-05-27T12:32:29Z","https://github.com/nuxt/ui/issues/4232",0.73904604,["Reactive",3039],{},["Set"],["ShallowReactive",3042],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fkux82NwaQa-gRA9NA6zZHstlGKuuExDOy69OGbD-DvU":-1},"/nuxt/ui/4323"]