\n \u003C/UChip>\n\u003C/template>\n````\n\n### Description\n\nHey,\n\nThanks for your great work.\n\nI have noticed this on a few elements in UI3, but especaily here padding just is not right. Yes of course you can change it, but i belive there needs to be some sane defaults across all elements.\n\nText in chip, and even a simple number is almost unreadable see screenshot below. Happy to open a pr or list all other elements where this seems to have happened (one that comes to mind is UAvatar https://github.com/nuxt/ui/issues/3558).\n\n\n\n### Additional context\n\nThis example is directly from the UI website",[3052,3053,3056],{"name":3019,"color":3020},{"name":3054,"color":3055},"v3","49DCB8",{"name":3057,"color":3058},"triage","ffffff",3633,"ui","Default padding on `UChip`","2025-03-20T09:21:01Z","https://github.com/nuxt/ui/issues/3633",0.73167634,{"description":3066,"labels":3067,"number":3070,"owner":3022,"repository":3044,"state":3071,"title":3072,"updated_at":3073,"url":3074,"score":3075},"https://volta.s3.fr-par.scw.cloud/Clean_Shot_2022_05_23_at_16_23_53_7945ec0dde.mp4\n",[3068],{"name":3019,"color":3069},"ff281a",555,"closed","[Nuxt3] Children pages reloads on first query param change","2022-11-17T11:45:24Z","https://github.com/nuxt/nuxt.com/issues/555",0.69742775,{"description":3077,"labels":3078,"number":3070,"owner":3022,"repository":3023,"state":3071,"title":3082,"updated_at":3083,"url":3084,"score":3075},"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`",[3079],{"name":3080,"color":3081},"vitest-environment","b60205","Tests fail when using .client components","2023-12-02T00:27:10Z","https://github.com/nuxt/test-utils/issues/555",{"description":3086,"labels":3087,"number":3091,"owner":3022,"repository":3060,"state":3071,"title":3092,"updated_at":3093,"url":3094,"score":3095},"### 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```",[3088,3089,3090],{"name":3019,"color":3020},{"name":3054,"color":3055},{"name":3057,"color":3058},3606,"Numbers in InputMenu component cause error in filter","2025-03-24T20:38:15Z","https://github.com/nuxt/ui/issues/3606",0.70504564,{"description":3097,"labels":3098,"number":3104,"owner":3022,"repository":3060,"state":3071,"title":3105,"updated_at":3106,"url":3107,"score":3108},"### Environment\n\n- Operating System: Darwin\n- Node Version: v23.7.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: bun\n- Builder: -\n- Runtime Modules: @nuxt/ui-pro@3.0.0-alpha.12\n- Build Modules: -\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha12\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/hidden-snow-d6s8wz?workspaceId=ws_JNWrpb8H73oZGFCJNwBaqL\n\n### Description\n\nWhen using the USelectMenu within a UModal, the search input of the select menu is not working correctly.\n\nIt can't be focused and typing only focuses the SelectMenu itself.\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3099,3100,3103],{"name":3019,"color":3020},{"name":3101,"color":3102},"duplicate","cfd3d7",{"name":3054,"color":3055},3288,"USelectMenu broken within UModal","2025-02-11T14:11:07Z","https://github.com/nuxt/ui/issues/3288",0.7140486,{"description":3110,"labels":3111,"number":3112,"owner":3022,"repository":3044,"state":3071,"title":3113,"updated_at":3114,"url":3115,"score":3116},"https://nuxt.com/docs/api/utils/call-once\n\n",[],1810,"% is in title for OG image","2025-03-19T09:28:40Z","https://github.com/nuxt/nuxt.com/issues/1810",0.71525383,{"description":3118,"labels":3119,"number":3035,"owner":3022,"repository":3044,"state":3071,"title":3121,"updated_at":3122,"url":3123,"score":3039},"",[3120],{"name":3019,"color":3069},"[Auth] Invite link does not work when not connected","2023-02-15T12:32:49Z","https://github.com/nuxt/nuxt.com/issues/735",["Reactive",3125],{},["Set"],["ShallowReactive",3128],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fEf6C23JAUGQpKjVR7QZfYlIj_WvgRMO-eQZCnSQYmQM":-1},"/nuxt/nuxt.com/684"]