\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.",[3137,3140,3143,3146,3149],{"name":3138,"color":3139},"bug","d73a4a",{"name":3141,"color":3142},"needs reproduction","CB47CF",{"name":3144,"color":3145},"v3","49DCB8",{"name":3147,"color":3148},"triage","ffffff",{"name":3150,"color":3151},"closed-by-bot","ededed",2859,"nuxt","ui","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":3161,"labels":3162,"number":3165,"owner":3153,"repository":3154,"state":3155,"title":3166,"updated_at":3167,"url":3168,"score":3169},"### 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```",[3163,3164],{"name":3138,"color":3139},{"name":3144,"color":3145},4355,"The UInput component is not a controlled component","2025-06-16T10:45:31Z","https://github.com/nuxt/ui/issues/4355",0.6970363,{"description":3171,"labels":3172,"number":3178,"owner":3153,"repository":3154,"state":3155,"title":3179,"updated_at":3180,"url":3181,"score":3182},"### 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```",[3173,3174,3175,3176],{"name":3138,"color":3139},{"name":3147,"color":3148},{"name":3150,"color":3151},{"name":3177,"color":3151},"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":3184,"labels":3185,"number":1235,"owner":3153,"repository":3153,"state":3155,"title":3192,"updated_at":3193,"url":3194,"score":3195},"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",[3186,3189],{"name":3187,"color":3188},"3.x","29bc7f",{"name":3190,"color":3191},"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":3197,"labels":3198,"number":3203,"owner":3153,"repository":3154,"state":3155,"title":3204,"updated_at":3205,"url":3206,"score":3207},"### Description\n\nIn InputNumber, the props used for the Increment and Decrement button are not passed to their slots, this causes difficulty in attempting to access those props in the case functionality needs to be added/overridden, but aesthetics (or ARIA) want to be maintained.\n\nThe increment button is an example of this, whereby `incrementIcon`, `color`, `size`, the translation, and the v-bind props for the button aren't passed to the slot. Thus, to access them again, code needs to be duplicated in order to recompute these properties, and defeats the purpose of DRY code. https://github.com/nuxt/ui/blob/f761369888c49fd0ee0f028dcf3c55dd5fbd2cae/src/runtime/components/InputNumber.vue#L176-L185\n\nA possible, simple solution might look like this (using scoped slots):\n```vue\n \u003Cslot name=\"increment\" :icon=\"incrementIcon\" :color=\"color\" :size=\"size\" :aria-label=\"t('inputNumber.increment')\" variant=\"link\" :bind=\"typeof increment === 'object' ? increment : undefined\"> \n \u003CUButton \n :icon=\"incrementIcon\" \n :color=\"color\" \n :size=\"size\" \n variant=\"link\" \n :aria-label=\"t('inputNumber.increment')\" \n v-bind=\"typeof increment === 'object' ? increment : undefined\" \n /> \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",[3199,3202],{"name":3200,"color":3201},"enhancement","a2eeef",{"name":3144,"color":3145},4435,"InputNumber increment/decrement button props not being passed to their respective slots","2025-08-17T13:50:25Z","https://github.com/nuxt/ui/issues/4435",0.73485446,{"description":3209,"labels":3210,"number":3216,"owner":3153,"repository":3154,"state":3155,"title":3217,"updated_at":3218,"url":3219,"score":3220},"### 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```",[3211,3212,3213,3214,3215],{"name":3138,"color":3139},{"name":3144,"color":3145},{"name":3147,"color":3148},{"name":3150,"color":3151},{"name":3177,"color":3151},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":3222,"labels":3223,"number":3227,"owner":3153,"repository":3154,"state":3155,"title":3228,"updated_at":3229,"url":3230,"score":3231},"### 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```",[3224,3225,3226],{"name":3138,"color":3139},{"name":3144,"color":3145},{"name":3147,"color":3148},4232,"[UProgress]: replace v-model with :value?","2025-05-27T12:32:29Z","https://github.com/nuxt/ui/issues/4232",0.73904604,{"description":3233,"labels":3234,"number":3238,"owner":3153,"repository":3154,"state":3155,"title":3239,"updated_at":3240,"url":3241,"score":3242},"### 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\n\nNuxt\n\n### Version\n\nv3.2.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/dreamy-euler-9595k7\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```",[3235,3236,3237],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},4452,"UTable context menu error during selection of items","2025-07-13T16:34:46Z","https://github.com/nuxt/ui/issues/4452",0.7395233,{"labels":3244,"number":3249,"owner":3153,"repository":3153,"state":3155,"title":3250,"updated_at":3251,"url":3252,"score":3253},[3245,3248],{"name":3246,"color":3247},"pending triage","E99695",{"name":3190,"color":3191},8456,"Missing BigInt support in nuxt.config.publicRuntimeConfig","2023-01-22T15:38:23Z","https://github.com/nuxt/nuxt/issues/8456",0.7435785,{"description":3255,"labels":3256,"number":3262,"owner":3153,"repository":3154,"state":3155,"title":3263,"updated_at":3264,"url":3265,"score":3266},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.16.0\n- Nuxt Version: 3.17.4\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: npm@10.9.2\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0.0\n\n### Reproduction\n\nYou can check in docs page and in this video.\nhttps://github.com/user-attachments/assets/a3e294dd-7ff2-4918-aea2-6b4e33409ff9\n\n### Description\n\nHi, thanks for the new update — it's very complete and appreciated!\nI think the PinInput should go back to the previous input when the type is set to number, instead of setting the value to 0. This is already the behavior when the type is text.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3257,3258,3259],{"name":3138,"color":3139},{"name":3144,"color":3145},{"name":3260,"color":3261},"reka-ui","56d799",4288,"PinInput should return to the previous input instead of setting zero","2025-06-18T09:26:52Z","https://github.com/nuxt/ui/issues/4288",0.74399424,["Reactive",3268],{},["Set"],["ShallowReactive",3271],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fkux82NwaQa-gRA9NA6zZHstlGKuuExDOy69OGbD-DvU":-1},"/nuxt/ui/4323"]