\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",[2865,2868,2871],{"name":2866,"color":2867},"bug","d73a4a",{"name":2869,"color":2870},"v3","49DCB8",{"name":2872,"color":2873},"triage","ffffff",3633,"nuxt","ui","open","Default padding on `UChip`","2025-03-20T09:21:01Z","https://github.com/nuxt/ui/issues/3633",0.78534,{"description":2883,"labels":2884,"number":2891,"owner":2875,"repository":2892,"state":2893,"title":2894,"updated_at":2895,"url":2896,"score":2897},"\r\nWhen you click 'Setup' navigation link nothing happend. 'Setup' tab on the left also does not get highlighted.\r\n\r\n",[2885,2888],{"name":2886,"color":2887},"documentation","0075ca",{"name":2889,"color":2890},"v0","4137F6",282,"test-utils","closed","Documentation. Page api-reference/setup/ suggests navigate to herself","2024-05-01T16:04:38Z","https://github.com/nuxt/test-utils/issues/282",0.4657956,{"description":2899,"labels":2900,"number":2905,"owner":2875,"repository":2876,"state":2893,"title":2906,"updated_at":2907,"url":2908,"score":2909},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.8\n\n### Description\n\n```vue\n\u003Cscript setup lang=\"ts\">\ntype Data = {\n id:number,\n name:string\n}\n\nconst defaultData = [\n {\n id: 1,\n name: \"a\"\n },\n {\n id: 2,\n name: \"b\"\n }\n]\n\nconst data = ref\u003CData[]>([])\nconst rerender = () => {\n if (!data.value?.length) {\n data.value = defaultData\n } else {\n data.value = []\n }\n}\n\u003C/script>\n\n\u003Ctemplate>\n \u003Cdiv>\n \u003CUButton label=\"rerender\" @click=\"rerender()\" />\n \u003CUTable :data=\"data\">\n \u003Ctemplate #empty>\n no data\n \u003C/template>\n \u003C/UTable>\n \u003C/div>\n\u003C/template>\n\n````\nIn this example, if the table's data is initially empty and then updated (by clicking the \"rerender\" button), you will notice that the content in the empty slot disappears. This indicates that the table's data is no longer empty, yet nothing is rendered in the table. The reason is that the table's columns are not reactive. I believe this limitation is caused by TanStack.\n\n### Potential Solution\n```vue\nwatch(columns, (newColumns) => {\n tableApi.setOptions((prevOpt) => ({\n ...prevOpt,\n columns: newColumns \n }))\n}) \n```\n\n\n\n\n### Additional context\n\n```vue\n\u003Cscript setup lang=\"ts\">\nimport { watch } from 'vue'\nimport { getCoreRowModel, useVueTable } from '@tanstack/vue-table'\ntype Data = {\n id: number,\n name: string\n}\n\nconst defaultData = [\n {\n id: 1,\n name: \"a\"\n },\n {\n id: 2,\n name: \"b\"\n }\n]\n\nconst data = ref\u003CData[]>([])\nconst columns = computed(() => Object.keys(data.value[0] ?? {}).map((accessorKey: string) => ({ accessorKey, header: accessorKey })))\n\nconst tableApi = useVueTable({\n data,\n columns: columns.value,\n getCoreRowModel: getCoreRowModel()\n})\n\nconst rerender = () => {\n if (!data.value.length) {\n\n data.value = defaultData\n } else {\n data.value = []\n }\n}\n\n/* watch(columns, (newColumns) => {\n tableApi.setOptions((prevOpt) => ({\n ...prevOpt,\n columns: newColumns \n }))\n}) */\n\u003C/script>\n\n\u003Ctemplate>\n \u003Cdiv>\n \u003CUButton label=\"rerender\" @click=\"rerender()\" />\n \u003Cdiv>\n {{ columns }}\n \u003C/div>\n \u003Cbr>\n \u003Cdiv>\n {{ tableApi.options }}\n \u003C/div>\n \u003C/div>\n\u003C/template>\n\n```\n\nnoticed that tableApi's columns won't change along with updates to the data",[2901,2904],{"name":2902,"color":2903},"enhancement","a2eeef",{"name":2869,"color":2870},2689,"[Table] reactive columns for auto-generated UTable columns","2024-11-21T13:11:03Z","https://github.com/nuxt/ui/issues/2689",0.7349272,{"description":2911,"labels":2912,"number":2913,"owner":2875,"repository":2914,"state":2893,"title":2915,"updated_at":2916,"url":2917,"score":2918},"",[],1269,"nuxt.com","[Workshop] Add Dates","2023-10-10T14:44:45Z","https://github.com/nuxt/nuxt.com/issues/1269",0.7647048,{"description":2920,"labels":2921,"number":2925,"owner":2875,"repository":2876,"state":2893,"title":2926,"updated_at":2927,"url":2928,"score":2929},"### Description\n\nsimilar github.com home page\r\n\r\n\n\n### Additional context\n\n_No response_",[2922],{"name":2923,"color":2924},"feature","A27AF6",814,"I would like to ask, have you considered making a new component: timeline?","2025-05-30T13:27:12Z","https://github.com/nuxt/ui/issues/814",0.7662572,{"labels":2931,"number":2934,"owner":2875,"repository":2875,"state":2893,"title":2935,"updated_at":2936,"url":2937,"score":2938},[2932],{"name":2886,"color":2933},"5319e7",13653,"Documentation progress","2025-02-22T22:32:21Z","https://github.com/nuxt/nuxt/issues/13653",0.7669896,{"description":2940,"labels":2941,"number":2947,"owner":2875,"repository":2875,"state":2893,"title":2948,"updated_at":2949,"url":2950,"score":2951},"Currently it appears there is only support for page level transitions. There is a workaround suggested [here](https://github.com/nuxt/nuxt.js/issues/108) but as you can see this gives concurrent transitions (ie. `mode` is not respected so enter/leave transitions are triggered at the same time).\r\n\r\nI think [this suggestion](https://github.com/nuxt/nuxt.js/issues/1054#issuecomment-314109892) makes sense. Though it might be best to specify a global setting in `nuxt.config.js` and then allow this setting to be overridden somehow (ie. in the layout component).\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This feature request is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1352\">#c1352\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2942,2944],{"name":2902,"color":2943},"8DEF37",{"name":2945,"color":2946},"2.x","d4c5f9",1519,"Add support for layout transitions","2023-01-18T15:41:52Z","https://github.com/nuxt/nuxt/issues/1519",0.76935536,{"description":2953,"labels":2954,"number":2961,"owner":2875,"repository":2914,"state":2893,"title":2962,"updated_at":2963,"url":2964,"score":2965},"### Environment\r\n\r\nFirefox Browser on Windows\r\n\r\n### Reproduction\r\n\r\nN/A\r\n\r\n### Describe the bug\r\n\r\nText is aggressively wrapped in `\u003Ccode>` blocks inside a table, so the Lifecycle Hooks page is difficult to read.\r\n\r\n\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2955,2958],{"name":2956,"color":2957},"duplicate","cfd3d7",{"name":2959,"color":2960},"responsive","1cd1c6",1400,"Documentation Lifecycle Hooks code blocks is aggresively wrapped","2023-12-08T15:49:41Z","https://github.com/nuxt/nuxt.com/issues/1400",0.7708562,{"labels":2967,"number":2970,"owner":2875,"repository":2875,"state":2893,"title":2971,"updated_at":2972,"url":2973,"score":2974},[2968,2969],{"name":2902,"color":2943},{"name":2945,"color":2946},6321,"Layout change transition","2023-01-22T15:50:56Z","https://github.com/nuxt/nuxt/issues/6321",0.7748335,{"description":2976,"labels":2977,"number":2985,"owner":2875,"repository":2875,"state":2893,"title":2986,"updated_at":2987,"url":2988,"score":2989},"### Describe the feature\n\nThe current implementation of the experimental ViewTransition plugin is great, but it can be limiting not having the actual transition object returned by 'document.startViewTransition'. This object can be used to wait for certain events during the transition (eg.: finished).\r\n\r\nIt would be great to receive this object from nuxt when one is created.\r\nThis would be needed in Elks (in-progress) view transition implementation as described in this issue here: https://github.com/elk-zone/elk/pull/2211#issuecomment-1974770960\n\n### Additional information\n\n- [X] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2978,2979,2982],{"name":2902,"color":2943},{"name":2980,"color":2981},"3.x","29bc7f",{"name":2983,"color":2984},"🍰 p2-nice-to-have","0E8A16",26044,"Provide a way to obtain the ongoing ViewTransition object","2024-03-06T15:58:41Z","https://github.com/nuxt/nuxt/issues/26044",0.77705574,["Reactive",2991],{},["Set"],["ShallowReactive",2994],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fGoDPAW3TSxw02FT_PgAMuFBd03FZYJFY7XOth-XgJ1o":-1},"/nuxt/nuxt.com/282"]