\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",[2885,2888,2889],{"name":2886,"color":2887},"bug","d73a4a",{"name":2871,"color":2872},{"name":2874,"color":2875},3633,"Default padding on `UChip`","2025-03-20T09:21:01Z","https://github.com/nuxt/ui/issues/3633",0.74838424,{"description":2896,"labels":2897,"number":2901,"owner":2857,"repository":2877,"state":2859,"title":2902,"updated_at":2903,"url":2904,"score":2905},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.4.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.16.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.14.4\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.9, nuxt-auth-sanctum@0.5.2, @vueuse/nuxt@11.3.0, nuxt-file-storage@0.2.9\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.14.1592\n\n### Reproduction\n\n```vue\n\u003Cscript setup lang=\"ts\">\nconst bill = defineModel()\nconst calcStep = (value: int): int => value \u003C 1000 ? 100 : 500\n\u003C/script>\n\n\u003Ctemplate>\n \u003Cdiv class=\"flex gap-4 items-center\">\n от \u003CUInputNumber v-model=\"bill.from\" :min=\"0\" :max=\"bill.to || 10000\" :step=\"calcStep(bill.from)\" variant=\"soft\" class=\"max-w-32\" />\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.",[2898,2899,2900],{"name":2886,"color":2887},{"name":2871,"color":2872},{"name":2874,"color":2875},2859,"UInputNumber changes value on blur when not asked for","2024-12-08T12:04:52Z","https://github.com/nuxt/ui/issues/2859",0.75990254,{"description":2907,"labels":2908,"number":2914,"owner":2857,"repository":2877,"state":2915,"title":2916,"updated_at":2917,"url":2918,"score":2919},"### 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_",[2909,2910,2911],{"name":2886,"color":2887},{"name":2871,"color":2872},{"name":2912,"color":2913},"reka-ui","56d799",2350,"closed","[SelectMenu] Broken focus/tab index after selecting","2024-12-03T15:11:34Z","https://github.com/nuxt/ui/issues/2350",0.7043489,{"description":2921,"labels":2922,"number":2928,"owner":2857,"repository":2858,"state":2915,"title":2929,"updated_at":2930,"url":2931,"score":2932},"due to the listing order being a big influence in traffic for the agency page, would it be possible for the agencies to be presented in a random order when accessing the [Agencies page](https://nuxt.com/support/agencies) ?",[2923,2925],{"name":2868,"color":2924},"1ad6ff",{"name":2926,"color":2927},"marketing","f5c828",1048,"[Agencies] Present agencies in a random order","2023-10-10T14:45:03Z","https://github.com/nuxt/nuxt.com/issues/1048",0.7265565,{"description":2934,"labels":2935,"number":2940,"owner":2857,"repository":2877,"state":2915,"title":2941,"updated_at":2942,"url":2943,"score":2944},"### For what version of Nuxt UI are you asking this question?\n\nv3-alpha\n\n### Description\n\nI understand that during alpha phase, documentation might not always be up-to-date. However, it might be interesting to understand whether one should expect that features mentioned in documentation actually work (or it should be considered a bug if they don't).\n\nE.g., I cannot get slotting in tables (https://ui3.nuxt.dev/components/table#with-slots) to work. But I'm unsure, if this is just the docs being faster than the implementation or I should open a bug report.",[2936,2939],{"name":2937,"color":2938},"question","d876e3",{"name":2871,"color":2872},2505,"Is documentation of v3 in sync with implementation?","2024-10-31T16:14:37Z","https://github.com/nuxt/ui/issues/2505",0.72777003,{"description":2946,"labels":2947,"number":2950,"owner":2857,"repository":2858,"state":2915,"title":2951,"updated_at":2952,"url":2953,"score":2954},"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",[2948],{"name":2886,"color":2949},"ff281a",1041,"[Jobs] Error after API update","2023-06-06T12:14:28Z","https://github.com/nuxt/nuxt.com/issues/1041",0.7452668,{"description":2956,"labels":2957,"number":2959,"owner":2857,"repository":2858,"state":2915,"title":2960,"updated_at":2961,"url":2962,"score":2963},"\n\nThe select should be after the input text",[2958],{"name":2868,"color":2924},547,"[Project] Invert type and input on YAML fields","2022-05-23T15:16:52Z","https://github.com/nuxt/nuxt.com/issues/547",0.7474784,{"description":2965,"labels":2966,"number":2959,"owner":2857,"repository":2970,"state":2915,"title":2971,"updated_at":2972,"url":2973,"score":2963},"I've have run into use case that seems peculiar, but I wanted to pose it here in case it's something that would make sense to bundle into this package as an enhancement.\r\n\r\nPut simply, I needed to do something like `registerEndpoint`, but to be able to set it up _before the Nuxt app starts_. We've tried calling `registerEndpoint` as early as possible, but from what I've seen, this just mocks calls for once the Vue app is mounted to the window, not before.\r\n\r\nWhat I've landed on as a solution is have a Nuxt plugin that's only included for test runs which replaces the global `$fetch` with a mock implementation of `$fetch` wrapped in `vi.fn()`, plus a mock implementation of `$fetch.create`. That's coupled with an object that can be configured with the return values like so:\r\n\r\n```ts\r\nconst endpointMocks = {\r\n 'http://0.0.0.0:8000/api/1.0': {\r\n some: {\r\n endpoint: () => ({ ok: true }),\r\n },\r\n },\r\n};\r\n```\r\n\r\nRight now it catches any call that doesn't match a path in this object, and raises an error instead of making a request.\r\n\r\nIs this a feature that would be desirable to be included as part of `nuxt-vitest`? Or perhaps would this be better suited as its own module/package elsewhere?",[2967],{"name":2968,"color":2969},"vitest-environment","b60205","test-utils","enhancement: mocking $fetch before app starts (@sidebase/nuxt-auth)","2023-12-02T23:39:53Z","https://github.com/nuxt/test-utils/issues/547",["Reactive",2975],{},["Set"],["ShallowReactive",2978],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f8bVjV8SIng5LLQnego4tD9rffwkN32R0QOFEmU-b_bM":-1},"/nuxt/nuxt.com/1056"]