\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```",[1984,1987,1990],{"name":1985,"color":1986},"bug","d73a4a",{"name":1988,"color":1989},"v3","49DCB8",{"name":1991,"color":1992},"triage","ffffff",3606,"nuxt","ui","closed","Numbers in InputMenu component cause error in filter","2025-03-24T20:38:15Z","https://github.com/nuxt/ui/issues/3606",0.6597314,{"description":2002,"labels":2003,"number":2009,"owner":1994,"repository":1995,"state":1996,"title":2010,"updated_at":2011,"url":2012,"score":2013},"### 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_",[2004,2005,2006],{"name":1985,"color":1986},{"name":1988,"color":1989},{"name":2007,"color":2008},"reka-ui","56d799",2350,"[SelectMenu] Broken focus/tab index after selecting","2024-12-03T15:11:34Z","https://github.com/nuxt/ui/issues/2350",0.72097445,{"description":2015,"labels":2016,"number":2020,"owner":1994,"repository":1995,"state":1996,"title":2021,"updated_at":2022,"url":2023,"score":2024},"### 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_",[2017],{"name":2018,"color":2019},"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.7249188,{"description":2026,"labels":2027,"number":2030,"owner":1994,"repository":2031,"state":1996,"title":2032,"updated_at":2033,"url":2034,"score":2035},"https://volta.s3.fr-par.scw.cloud/Clean_Shot_2022_05_23_at_16_23_53_7945ec0dde.mp4\n",[2028],{"name":1985,"color":2029},"ff281a",555,"nuxt.com","[Nuxt3] Children pages reloads on first query param change","2022-11-17T11:45:24Z","https://github.com/nuxt/nuxt.com/issues/555",0.72815216,{"description":2037,"labels":2038,"number":2030,"owner":1994,"repository":2042,"state":1996,"title":2043,"updated_at":2044,"url":2045,"score":2035},"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`",[2039],{"name":2040,"color":2041},"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":2047,"labels":2048,"number":2050,"owner":1994,"repository":1995,"state":1996,"title":2051,"updated_at":2052,"url":2053,"score":2054},"### Description\n\nIs there a way to change the default row height of a table? Thanks!",[2049],{"name":2018,"color":2019},3032,"UTable row height","2025-01-08T10:01:46Z","https://github.com/nuxt/ui/issues/3032",0.7305412,{"description":2056,"labels":2057,"number":2061,"owner":1994,"repository":1995,"state":1996,"title":2062,"updated_at":2063,"url":2064,"score":2065},"### Description\n\nI tried using v-model with an array on Checkbox, but it is rendered as Button, inside a form it should render the native input like in Radix UI. This means the checkbox has no array support and any library expecting to access the native Input event will not work properly (required, invalid). \n\nI would like to understand why the Checkbox and Radio components have been implemented as button elements with ARIA attributes.",[2058,2059,2060],{"name":2018,"color":2019},{"name":1988,"color":1989},{"name":2007,"color":2008},3240,"Checkbox & Radio rendered as a button? No Native Input Element.","2025-02-05T09:14:50Z","https://github.com/nuxt/ui/issues/3240",0.7316907,{"description":2067,"labels":2068,"number":2069,"owner":1994,"repository":2070,"state":1996,"title":2071,"updated_at":2072,"url":2073,"score":2074},"Couldn't help but notice the \"is the next **null** release\". \n\n\n\nFor the version, the bumpType is defaulted to `patch` here:\n\nhttps://github.com/rijkvanzanten/fonts/blob/89bfccd85974f4670eebd307ea850b898209fb55/scripts/update-changelog.ts#L18\n\nbut used \"raw\" here:\n\nhttps://github.com/rijkvanzanten/fonts/blob/89bfccd85974f4670eebd307ea850b898209fb55/scripts/update-changelog.ts#L42\n\nThe `bumpType` isn't used anywhere outside these two, so moving the `|| 'patch'` fallback from line 18 to 16 should do the trick. PR incoming~",[],401,"fonts","Update-changelog script renders `null` as `bumpType` in message","2024-11-24T17:50:36Z","https://github.com/nuxt/fonts/issues/401",0.73422396,{"description":2076,"labels":2077,"number":2079,"owner":1994,"repository":2031,"state":1996,"title":2080,"updated_at":2081,"url":2082,"score":2083},"\n",[2078],{"name":1985,"color":2029},793,"[Home] Carousel not working in mobile","2022-07-21T16:26:32Z","https://github.com/nuxt/nuxt.com/issues/793",0.7356446,{"description":2085,"labels":2086,"number":2090,"owner":1994,"repository":1995,"state":1996,"title":2091,"updated_at":2092,"url":2093,"score":2094},"### 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```",[2087,2088,2089],{"name":1985,"color":1986},{"name":1988,"color":1989},{"name":2007,"color":2008},2657,"SelectMenu search not clickable from modal","2025-02-13T18:27:29Z","https://github.com/nuxt/ui/issues/2657",0.73591375,["Reactive",2096],{},["Set"],["ShallowReactive",2099],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"KpYGsIM0UqkTPvmCrNYelrwNCvEhIG0gxhRC0TyMMHQ":-1},"/nuxt/ui/3665"]