\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.",[2878,2881,2884],{"name":2879,"color":2880},"bug","d73a4a",{"name":2882,"color":2883},"v3","49DCB8",{"name":2885,"color":2886},"triage","ffffff",2859,"ui","UInputNumber changes value on blur when not asked for","2024-12-08T12:04:52Z","https://github.com/nuxt/ui/issues/2859",0.74116474,{"description":2894,"labels":2895,"number":2899,"owner":2868,"repository":2888,"state":2900,"title":2901,"updated_at":2902,"url":2903,"score":2904},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: 3.16.0\n- CLI Version: 3.22.5\n- Nitro Version: 2.11.6\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: devtools, modules, components, css, compatibilityDate\n- Runtime Modules: @nuxt/ui@3.0.0, @pinia/nuxt@0.10.1, compodium@0.1.0-beta.5\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\u003Ctemplate>\n \u003Cdiv>\n \u003CUInputMenu :items=\"idList\" v-model=\"value\" />\n \u003C/div>\n\u003C/template>\n\n\u003Cscript lang=\"ts\" setup>\nconst value = ref(0)\nconst idList = ref([168, 170, 203])\n\u003C/script>\n```\n\n### Description\n\nIf adding array of numbers to InputMenu the menu isn't closing after choosing a number.\nOnly way to close it is double-clicking on the dropdown arrow.\nThe Console shows an error in useFilter.\n\n### Additional context\n\n\n\n\n\n### Logs\n\n```shell-script\nUncaught (in promise) TypeError: string.normalize is not a function\n at contains (useFilter.js?v=87101672:23:21)\n at InputMenu.vue:114:18\n at wrappedFn (reactivity.esm-bundler.js?v=87101672:820:19)\n at Array.filter (\u003Canonymous>)\n at apply (reactivity.esm-bundler.js?v=87101672:828:27)\n at Proxy.filter (reactivity.esm-bundler.js?v=87101672:720:12)\n at InputMenu.vue:112:50\n at Array.map (\u003Canonymous>)\n at ComputedRefImpl.fn (InputMenu.vue:112:27)\n at refreshComputed (reactivity.esm-bundler.js?v=87101672:353:29)\n```",[2896,2897,2898],{"name":2879,"color":2880},{"name":2882,"color":2883},{"name":2885,"color":2886},3606,"closed","Numbers in InputMenu component cause error in filter","2025-03-24T20:38:15Z","https://github.com/nuxt/ui/issues/3606",0.68848777,{"description":2906,"labels":2907,"number":2911,"owner":2868,"repository":2888,"state":2900,"title":2912,"updated_at":2913,"url":2914,"score":2915},"### Environment\n\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v20.11.0\r\n- Nuxt Version: 3.13.0\r\n- CLI Version: 3.13.1\r\n- Nitro Version: 2.9.7\r\n- Package Manager: npm@10.2.4\r\n- Builder: -\r\n- User Config: compatibilityDate, runtimeConfig, experimental, router, i18n, devServer, devtools, app, components, modules, vue, tailwindcss, image, ui, nitro, storyblok, algolia, colorMode, hooks\r\n- Runtime Modules: @nuxt/devtools@1.4.1, @nuxt/image@1.8.0, @nuxt/ui@2.18.4, @nuxtjs/i18n@8.5.1, @pinia/nuxt@0.5.4, @storyblok/nuxt@6.0.10, @vueuse/nuxt@11.0.3, nuxt-og-image@3.0.0-rc.66, @stefanobartoletti/nuxt-social-share@1.0.1\r\n- Build Modules: -\r\n------------------------------\n\n### Version\n\nv2.18.4\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-y5b7nb?file=app.vue\n\n### Description\n\nWhen using the button component with color 'white' and variant 'link', 'outline' or 'soft' invalid Tailwind color classes are generated, e.g. 'text-white-500'. It should be 'text-white'.\r\n\r\ntext-white-500 hover:text-white-600 disabled:text-white-500 dark:text-white-400 dark:hover:text-white-500 dark:disabled:text-white-400 focus-visible:ring-inset focus-visible:ring-white-500 dark:focus-visible:ring-white-400\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2908],{"name":2909,"color":2910},"question","d876e3",2109,"White link, outline and soft buttons generate wrong Tailwind classes, e.g. 'text-white-500'","2024-09-06T13:10:25Z","https://github.com/nuxt/ui/issues/2109",0.70146185,{"description":2917,"labels":2918,"number":2921,"owner":2868,"repository":2869,"state":2900,"title":2922,"updated_at":2923,"url":2924,"score":2925},"https://volta.s3.fr-par.scw.cloud/Clean_Shot_2022_05_23_at_16_23_53_7945ec0dde.mp4\n",[2919],{"name":2879,"color":2920},"ff281a",555,"[Nuxt3] Children pages reloads on first query param change","2022-11-17T11:45:24Z","https://github.com/nuxt/nuxt.com/issues/555",0.7024964,{"description":2927,"labels":2928,"number":2921,"owner":2868,"repository":2932,"state":2900,"title":2933,"updated_at":2934,"url":2935,"score":2925},"I have some components that include \"client\" components (i.e. ClientComponent.client.vue). When I run tests for components that include client components, they always seem to fail with messages like this:\r\n\r\n```\r\n[Vue warn]: Component \u003CAnonymous>: setup function returned a promise, but no \u003CSuspense> boundary was found in the parent component tree. A component with async setup() must be nested in a \u003CSuspense> in order to be rendered. \r\n at \u003CClientComponent.client> \r\n at \u003CTestA ref=\"VTU_COMPONENT\" > \r\n at \u003CVTUROOT>\r\n```\r\n\r\nA simple component that I'm testing looks like this:\r\n\r\n\r\n```\r\n// TestA.vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CClientComponent />\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\nand the test file looks like this:\r\n\r\n\r\n```\r\n// TestA.spec.ts\r\nimport { describe, it, expect } from 'vitest';\r\nimport { mount } from '@vue/test-utils';\r\nimport TestA from './TestA.vue';\r\n\r\ndescribe('Competition TestA', () => {\r\n it('renders component', async () => {\r\n const wrapper = mount(TestA);\r\n expect(wrapper.text()).toContain('Client component here...');\r\n });\r\n});\r\n\r\n```\r\n\r\nFinally, the client component:\r\n\r\n```\r\n// ClientComponent.client.vue\r\n\u003Ctemplate>\r\n \u003Cdiv>Client component here...\u003C/div>\r\n\u003C/template>\r\n```\r\n\r\nIf I remove the \".client\" from the component file name (to make it just ClientComponent.vue), then the tests will run and pass normally. However, there are some cases where I want to use \".client\" to make sure it's only rendered client-side.\r\n\r\n### Reproduction \r\nhttps://stackblitz.com/edit/github-ndby6m?file=components/TestA.spec.ts\r\n\r\nFailures can be seen there by running `pnpm run test`",[2929],{"name":2930,"color":2931},"vitest-environment","b60205","test-utils","Tests fail when using .client components","2023-12-02T00:27:10Z","https://github.com/nuxt/test-utils/issues/555",{"description":2937,"labels":2938,"number":2942,"owner":2868,"repository":2869,"state":2900,"title":2943,"updated_at":2944,"url":2945,"score":2946},"Respectively to `contact@nuxt.com` / `support@nuxt.com` / `careers@nuxt.com`",[2939],{"name":2940,"color":2941},"enhancement","1ad6ff",503,"[Company] `contact` / `support` / `careers` forms should send an email","2023-02-15T12:32:26Z","https://github.com/nuxt/nuxt.com/issues/503",0.7062849,{"description":2948,"labels":2949,"number":2942,"owner":2868,"repository":2932,"state":2900,"title":2951,"updated_at":2952,"url":2953,"score":2946},"After updating happy-dom to the latest version **10.5.2** ,\r\nI have this error when I run my app : \r\n`Error while requiring module vitest-environment-nuxt/module: Error: Cannot find module '/Users/\u003Cuser>/\u003Cfolderpath>/vitest-environment-nuxt/module'`\r\n\r\nDoes anyone have a solution ?",[2950],{"name":2930,"color":2931},"Error after updating happy dom dependency","2023-12-02T00:17:10Z","https://github.com/nuxt/test-utils/issues/503",{"description":2955,"labels":2956,"number":2962,"owner":2868,"repository":2888,"state":2900,"title":2963,"updated_at":2964,"url":2965,"score":2966},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v20.12.2`\n- Nuxt Version: `3.14.159`\n- CLI Version: `3.15.0`\n- Nitro Version: `2.10.4`\n- Package Manager: `bun@1.1.33`\n- Builder: `-`\n- User Config: `default`\n- Runtime Modules: `@nuxt/ui@3.0.0-alpha.8`, `@nuxt/eslint@0.6.1`, `@vueuse/nuxt@11.2.0`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.8\n\n### Reproduction\n\nPlace SelectMenu with search in Modal then try to access search input\n\n### Description\n\nSelectMenu search not working from modal\nIt's working if :portal=\"false\", but style broken\n\n### Additional context\n\n\n\n\n### Logs\n\n```shell-script\n\n```",[2957,2958,2959],{"name":2879,"color":2880},{"name":2882,"color":2883},{"name":2960,"color":2961},"reka-ui","56d799",2657,"SelectMenu search not clickable from modal","2025-02-13T18:27:29Z","https://github.com/nuxt/ui/issues/2657",0.7106511,{"description":2968,"labels":2969,"number":2973,"owner":2868,"repository":2888,"state":2900,"title":2974,"updated_at":2975,"url":2976,"score":2977},"### Environment\n\n System:\n OS: Linux 6.5 Ubuntu 23.10 23.10 (Mantic Minotaur)\n CPU: (8) x64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz\n Memory: 44.48 GB / 62.57 GB\n Container: Yes\n Shell: 5.9 - /usr/bin/zsh\n Browsers:\n Chrome: 126.0.6478.126\n\n### Version\n\nv3.0.0-alpha.6\n\n### Reproduction\n\nhttps://ui3.nuxt.dev/components/select-menu\n\n### Description\n\n1. open docs\n2. open any select menu\n3. select any option\n4. tab to next field\n5. tab index is reset\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2970,2971,2972],{"name":2879,"color":2880},{"name":2882,"color":2883},{"name":2960,"color":2961},2350,"[SelectMenu] Broken focus/tab index after selecting","2024-12-03T15:11:34Z","https://github.com/nuxt/ui/issues/2350",0.7210876,["Reactive",2979],{},["Set"],["ShallowReactive",2982],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$frg1-zGhWq0cdwPG39ymNWkEcTm60qPUdOktcwoYRdlQ":-1},"/nuxt/test-utils/749"]