\n \u003CUInput v-model=\"state.name1\" placeholder=\"...\" />\n\u003C/UModal>\n```\n\nWhen a modal contains one or more input boxes, the first input box will always get focus automatically.\nIf I manually add a close button in the upper right corner, it will trigger a validation when I click it. This is not good. How can I avoid the input box getting focus when opening the modal?\n\n### Additional context\n\n\n\n\n### Logs\n\n```shell-script\n\n```",[2937,2940,2943,2946],{"name":2938,"color":2939},"bug","d73a4a",{"name":2941,"color":2942},"triage","ffffff",{"name":2944,"color":2945},"closed-by-bot","ededed",{"name":2947,"color":2945},"stale",3062,"The input box in the modal will automatically gain focus","2025-06-18T09:02:39Z","https://github.com/nuxt/ui/issues/3062",0.76638323,{"description":2954,"labels":2955,"number":2959,"owner":2911,"repository":2960,"state":2929,"title":2961,"updated_at":2962,"url":2963,"score":2964},"\n",[2956],{"name":2957,"color":2958},"enhancement","1ad6ff",600,"nuxt.com","[Resources] Showcases title can be hidden in favor of the select on mobile","2023-02-15T12:32:36Z","https://github.com/nuxt/nuxt.com/issues/600",0.7764023,{"description":2966,"labels":2967,"number":2959,"owner":2911,"repository":2912,"state":2929,"title":2975,"updated_at":2976,"url":2977,"score":2964},"\r\n\r\ni mountSuspended component use useFetch call rest api. Error as image.\r\n\r\nPlease help me!",[2968,2971,2974],{"name":2969,"color":2970},"vitest-environment","b60205",{"name":2972,"color":2973},"needs reproduction","DE7793",{"name":2944,"color":2945},"Test component call api","2023-12-10T01:51:31Z","https://github.com/nuxt/test-utils/issues/600",{"description":2979,"labels":2980,"number":2983,"owner":2911,"repository":2928,"state":2929,"title":2984,"updated_at":2985,"url":2986,"score":2987},"### For what version of Nuxt UI are you asking this question?\n\nv3.0.0-alpha.x\n\n### Description\n\n\n",[2981,2982],{"name":2922,"color":2923},{"name":2925,"color":2926},2910,"How to styling change year and month buttons ?","2025-03-24T18:00:29Z","https://github.com/nuxt/ui/issues/2910",0.77977073,{"description":2989,"labels":2990,"number":2996,"owner":2911,"repository":2928,"state":2929,"title":2997,"updated_at":2998,"url":2999,"score":3000},"### Description\n\nwhy the all the buttons and triggers does not have active state ? it has hover and focus but not active\n\n### Additional context\n\n_No response_",[2991,2993,2995],{"name":2957,"color":2992},"a2eeef",{"name":2994,"color":2942},"wontfix-v2",{"name":2925,"color":2926},991,"button active state ","2025-06-30T10:35:45Z","https://github.com/nuxt/ui/issues/991",0.79223514,{"description":3002,"labels":3003,"number":3006,"owner":2911,"repository":2928,"state":2929,"title":3007,"updated_at":3008,"url":3009,"score":3010},"### Description\n\nHello there,\n\nin `@nuxt/ui` v2 it was possible to access the buttons from inside `Tabs` or the input from `SelectMenu` via template refs to focus explicit elements. \nIs it possible to get that feature back especially for accessibility reasons?",[3004,3005],{"name":2922,"color":2923},{"name":2925,"color":2926},4292,"Exposing elements for better accessibility","2025-06-12T13:38:55Z","https://github.com/nuxt/ui/issues/4292",0.7949901,{"description":3012,"labels":3013,"number":3018,"owner":2911,"repository":2928,"state":2929,"title":3019,"updated_at":3020,"url":3021,"score":3022},"### Version\n\nv3 latest commit\n\n### Description\n\nI noticed the following behavior:\n\n- When the data prop of a `\u003CUTable>` changes, the rows dont get properly unmounted\n- This results in components within a row to never have `unMounted` being called (only if the amount of rows is less for the ones that get removed)\n- Further this can result in a bugs and unexpected behavior because for components only the props change but the setup function is not called again\n\n### Reproduction\n\nConsider the following simplified example. The badge never changes color. Also if one would use `onMounted`/`onUnmounted` within the badge component they would not get triggered when the data changes (only if the amount of rows change).\n\n**my-badge.vue**\n\n```vue\n\u003Cscript setup lang=\"ts\">\nconst props = defineProps\u003C{\n status: 'yes' | 'no';\n}>();\n\nswitch (props.status) {\n case 'yes':\n color = 'success';\n break;\n case 'no':\n color = 'error';\n break;\n}\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUBadge :color variant=\"subtle\">{{ props.status }}\u003C/UBadge>\n\u003C/template>\n```\n\n**my-table.vue**\n```vue\n\u003Cscript setup lang=\"ts\">\n const page = ref(1);\n const { data } = useFetch('url', { query: { page }}); // This gets refetched when `page.value` changes\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUTable :data :columns>\n \u003Ctemplate #status-cell=\"{ row }\">\n \u003CMyBadge :status=\"row.original.status\" />\n \u003C/template>\n \u003C/UTable>\n\u003C/template>\n```\n\n### Additional context\n\nI think this was already the case within v2: There I have a table that contains `\u003CNuxtImg />` tags. When the data changes (e.g. by pagination) the new rows are displayed with the images of the old row until the new images are loaded. That is probably because the `\u003CNuxtImg />` components dont get removed and replaced by all new ones.\n\nLet me know if I should create a reproduction repo\n",[3014,3015,3017],{"name":2938,"color":2939},{"name":2972,"color":3016},"CB47CF",{"name":2925,"color":2926},3043,"Table rows dont get deleted / unmounted when data changes","2025-03-28T17:35:58Z","https://github.com/nuxt/ui/issues/3043",0.80138254,{"description":3024,"labels":3025,"number":3028,"owner":2911,"repository":2928,"state":2929,"title":3029,"updated_at":3030,"url":3031,"score":3032},"### Environment\n\nOperating System: Windows_NT\nNode Version: v20.15.0\nNuxt Version: 3.13.2\nCLI Version: 3.14.0\nNitro Version: 2.9.7\nPackage Manager: pnpm@9.10.0\nBuilder: -\nUser Config: -\nRuntime Modules: -\nBuild Modules: -\n\n### Version\n\nv3.0.0-alpha.5\n\n### Reproduction\n\nNo need. It'd be great if we had a stackblitz or codepen etc. playground example repo for v3 so that everyone can get a repo up quickly. It'd increase feedback.\n\n### Description\n\nI think I found something. Created a new project, added v3 and set `colorMode` to 'light' but it is still dark. Cleared local and session storage and cookies and cache. Still dark. Anyone having the same problem?\nRemoving `@import \"@nuxt/ui\";` from my app.vue changes the theme to light. html tag has `class=\"light\"`\n\nInspected elements and saw that color-scheme is incorrect. It has both light and dark. Changing it to light changes the mode to light. Is this correct?\n\n\nAdding this solves the problem, but it doesn't look viable.\n```\n:root {\n color-scheme: light;\n}\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3026,3027],{"name":2938,"color":2939},{"name":2925,"color":2926},2320,"Dark/light mode problem","2024-10-07T17:53:06Z","https://github.com/nuxt/ui/issues/2320",0.801477,["Reactive",3034],{},["Set"],["ShallowReactive",3037],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f-HzaeuM0HO4VAATB3Peu8muEmtaNL0oNvO_LrFO7mvA":-1},"/nuxt/ui/4395"]