\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",[2025,2026,2027],{"name":1985,"color":1986},{"name":1991,"color":1992},{"name":2028,"color":2029},"triage","ffffff",3633,"Default padding on `UChip`","2025-03-20T09:21:01Z","https://github.com/nuxt/ui/issues/3633",0.7257323,{"description":2036,"labels":2037,"number":2041,"owner":1994,"repository":2017,"state":2042,"title":2043,"updated_at":2044,"url":2045,"score":2046},"Blocked by #720 ",[2038],{"name":2039,"color":2040},"enhancement","1ad6ff",684,"closed","[Community] Nuxters filter to select community only","2022-07-25T13:34:54Z","https://github.com/nuxt/nuxt.com/issues/684",0.45146516,{"description":2048,"labels":2049,"number":2052,"owner":1994,"repository":2017,"state":2042,"title":2053,"updated_at":2054,"url":2055,"score":2056},"https://volta.s3.fr-par.scw.cloud/Clean_Shot_2022_05_23_at_16_23_53_7945ec0dde.mp4\n",[2050],{"name":1985,"color":2051},"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.69365525,{"description":2058,"labels":2059,"number":2052,"owner":1994,"repository":2008,"state":2042,"title":2063,"updated_at":2064,"url":2065,"score":2056},"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`",[2060],{"name":2061,"color":2062},"vitest-environment","b60205","Tests fail when using .client components","2023-12-02T00:27:10Z","https://github.com/nuxt/test-utils/issues/555",{"description":2067,"labels":2068,"number":2072,"owner":1994,"repository":1995,"state":2042,"title":2073,"updated_at":2074,"url":2075,"score":2076},"### 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```",[2069,2070,2071],{"name":1985,"color":1986},{"name":1991,"color":1992},{"name":2028,"color":2029},3606,"Numbers in InputMenu component cause error in filter","2025-03-24T20:38:15Z","https://github.com/nuxt/ui/issues/3606",0.70152146,{"description":2078,"labels":2079,"number":2080,"owner":1994,"repository":2017,"state":2042,"title":2081,"updated_at":2082,"url":2083,"score":2084},"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.702836,{"description":2086,"labels":2087,"number":2089,"owner":1994,"repository":2017,"state":2042,"title":2090,"updated_at":2091,"url":2092,"score":2093},"After updating the API, Jobs page is on error under certain circumstances : \n\nRelated commit : https://github.com/nuxtlabs/nuxt.com/commit/8962705b5d0dda99724d661efeeb4ed18e332db4\n\nEnvironment (Preview) : https://framework-p2aadzhns-nuxt-js.vercel.app/\n\n```\nTypeError: Cannot read properties of undefined (reading 'map')\n```\n\nThis is due to changes in the data structure of the API, changing from `\u003CNuxtJob[]>` to `{ data: \u003CNuxtJob[]>`. API endpoint (/api/jobs) seems to sometimes serve the outdated data.\n\n- 1 : client-side navigation from / to /support/jobs : fails\n- 2 : Server hit on /support/jobs : works\n- 3: client-side navigation back and forth to /support/jobs after 2 : works",[2088],{"name":1985,"color":2051},1041,"[Jobs] Error after API update","2023-06-06T12:14:28Z","https://github.com/nuxt/nuxt.com/issues/1041",0.7120688,["Reactive",2095],{},["Set"],["ShallowReactive",2098],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"gRIBJbOTEQ3wDVVoDxhe9aSktnsbDZEF_IGzTB2tDVY":-1},"/nuxt/test-utils/684"]