\n\u003C/UCard>\n```\n\n### Description\n\nIf using a UTable component on a background that isn't the default neutral color the bg-color of the thead is visible.\n\n\n\n\n\n_A little bit easier to see with white Background_\n\n\n\n\nMaybe this is a wanted behavior. So if so please ignore and close the issue.\nI know sometimes you want a background color in the headlines. But sometimes you don't want them.\nAnyways if this is a wanted behavior, then maybe this issue will help those who don't want a background color and are looking for a solution.\n\n### Additional context\n\nCould be fixed by adding:\n```vue\n:ui=\"{\n thead: 'bg-unset'\n}\"\n```\nto the `\u003CUTable>` tag\n\n\n\n### Logs\n\n```shell-script\n-\n```",[2887,2888,2891],{"name":2868,"color":2869},{"name":2889,"color":2890},"v3","49DCB8",{"name":2874,"color":2875},3607,"Background-Color for UTable","2025-03-18T15:08:25Z","https://github.com/nuxt/ui/issues/3607",0.632945,{"description":2898,"labels":2899,"number":2904,"owner":2877,"repository":2878,"state":2879,"title":2905,"updated_at":2906,"url":2907,"score":2908},"### Description\n\nHow can I assign an ID to a tab so that I can scroll directly to it?\nCurrently, I’m working around this by giving the div inside the slot (i.e. the tab content) an ID. When the tab is opened, I scroll to that ID manually.\n\n```\n\u003Ctemplate>\n \u003CUAccordion\n v-model=\"currentOpen\"\n :ui=\"accordionStyle\"\n :items=\"items\"\n >\n \u003Ctemplate #component=\"{ item }\">\n \u003Ccomponent\n :is=\"getComponent((item as CustomAccordionItem).componentName)\"\n :id=\"(item as CustomAccordionItem).sectionKey\"\n :section-key=\"(item as CustomAccordionItem).sectionKey\"\n @section-mounted=\"sectionMounted\"\n />\n \u003C/template>\n \u003C/UAccordion>\n\u003C/template>\n```\n\ndid i miss something?\n\n### Additional context\n\n_No response_",[2900,2903],{"name":2901,"color":2902},"enhancement","a2eeef",{"name":2874,"color":2875},3868,"Allow assigning IDs to Nuxt UI Tab panels for scroll targeting","2025-04-12T08:35:52Z","https://github.com/nuxt/ui/issues/3868",0.6638386,{"description":2910,"labels":2911,"number":2914,"owner":2877,"repository":2915,"state":2916,"title":2917,"updated_at":2918,"url":2919,"score":2920},"",[2912],{"name":2901,"color":2913},"1ad6ff",611,"nuxt.com","closed","[Resources] Refactor showcases into a composable","2023-02-15T12:32:38Z","https://github.com/nuxt/nuxt.com/issues/611",0.6339708,{"description":2922,"labels":2923,"number":2914,"owner":2877,"repository":2927,"state":2916,"title":2928,"updated_at":2929,"url":2930,"score":2920},"I'm on v0.11.2 and it seems what `defineVitestConfig` wants and the type definition doesn't line up?\r\n\r\nIt wants an `InlineConfig` passed in directly in the typedef, but I'm having to do this:\r\n\r\n```js\r\nimport { defineVitestConfig } from \"nuxt-vitest/config\";\r\nimport type { InlineConfig } from \"vitest\";\r\n\r\nconst test: InlineConfig = {\r\n coverage: {\r\n all: true,\r\n branches: 87.5, // 7 / 8\r\n exclude: [\r\n \"node_modules\",\r\n \".nuxt\",\r\n \"app\",\r\n \"dist\",\r\n \"scripts\",\r\n \"*.config.ts\",\r\n \"**/types.ts\",\r\n \"**/*.tests.ts\",\r\n \"**/*.js\",\r\n \"**/*.mjs\",\r\n \"pages\",\r\n \"plugins\",\r\n \"app.vue\",\r\n ],\r\n },\r\n environment: \"happy-dom\",\r\n include: [\"**/*.tests.ts\"],\r\n};\r\n\r\n// eslint-disable-next-line @typescript-eslint/ban-ts-comment\r\n// @ts-ignore\r\nexport default defineVitestConfig({ test });\r\n```",[2924],{"name":2925,"color":2926},"vitest-environment","b60205","test-utils","typecheck issues with defineVitestConfig?","2023-12-02T23:35:07Z","https://github.com/nuxt/test-utils/issues/611",{"description":2932,"labels":2933,"number":2936,"owner":2877,"repository":2878,"state":2916,"title":2937,"updated_at":2938,"url":2939,"score":2940},"### Description\n\nIt's shorter and can save traffic.\n\n### Additional context\n\n_No response_",[2934,2935],{"name":2901,"color":2902},{"name":2889,"color":2890},3250,"Use `foo-(--bar)` instead of `foo-[var(--bar)]` for tailwindcss classes","2025-02-07T10:24:17Z","https://github.com/nuxt/ui/issues/3250",0.63461685,{"description":2942,"labels":2943,"number":2944,"owner":2877,"repository":2915,"state":2916,"title":2945,"updated_at":2946,"url":2947,"score":2948},"On the 'Enterprise Jobs' page, location badges were closely together on mobile screens. I removed the `mr-3` class from the badge element and placed the badges inside a parent `\u003Cdiv>` with the classes` flex`, `flex-wrap`, and `gap-3` Now it won't stick together and will look good on mobile devices.\r\n\r\n| **BEFORE** | **AFTER** | \r\n|-------- | ------ | \r\n|  |  |\r\n\r\n\r\n\r\n\n```[tasklist]\n### Tasks\n```\n",[],1403,"Spacing issue with Location badges on 'Enterprise Jobs' page for mobile screens","2024-09-19T19:38:43Z","https://github.com/nuxt/nuxt.com/issues/1403",0.6395113,{"description":2950,"labels":2951,"number":2957,"owner":2877,"repository":2878,"state":2916,"title":2958,"updated_at":2959,"url":2960,"score":2961},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v18.20.5\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.8.2\n- Builder: -\n- User Config: default\n- Runtime Modules: nuxt-vuefire@1.0.4, @nuxt/ui@3.0.0-alpha.9\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.9\n\n### Reproduction\n\n\n\n\n\n```\n \u003CUTooltip :delay-duration=\"0\" :text=\"`R$ ${transactionCost.brl}`\">\n \u003CUIcon class=\"text-yellow-500 text-xs\" name=\"i-lucide-coins\" />\n \u003Cp class=\"text-neutral-200 text-xs\">\n {{ transactionCost.credits }}\n \u003C/p>\n\u003C/UTooltip>\n```\n\n``` \n\u003CNuxtLayout>\n \u003CUApp :toaster=\"{ position: 'top-right' }\">\n \u003CNuxtPage />\n \u003C/UApp>\n\u003C/NuxtLayout>\n```\n\n\n### Description\n\nThe `app.vue` is already using the `UApp`. When I try to add a `UTooltip` inside the modal, it throw an error.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```\nUncaught (in promise) Error: Injection `Symbol(TooltipProviderContext)` not found. Component must be used within `TooltipProvider`\n```",[2952,2953,2956],{"name":2868,"color":2869},{"name":2954,"color":2955},"needs reproduction","CB47CF",{"name":2889,"color":2890},2801,"[v3][UTooltip] `UTooltip` inside `UModal` causing error","2025-02-06T15:28:30Z","https://github.com/nuxt/ui/issues/2801",0.6421014,{"description":2963,"labels":2964,"number":2971,"owner":2877,"repository":2877,"state":2916,"title":2972,"updated_at":2973,"url":2974,"score":2975},"### Environment\r\n\r\nNuxt project info: 12:42:28\r\n\r\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v16.16.0`\r\n- Nuxt Version: `3.2.3`\r\n- Nitro Version: `2.2.3`\r\n- Package Manager: `npm@8.11.0`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://github.com/beyer-johannes/use-fetch-pending-initial-true\r\n\r\n### Describe the bug\r\n\r\nUsing useFetch with {immediate:false} option is initial true.\r\n\r\n```\r\nconst { pending, execute } = useFetch(\r\n \"https://api.chucknorris.io/jokes/random\",\r\n {\r\n immediate: false,\r\n }\r\n);\r\n\r\n// pending.value === true without execute call.\r\n```\r\n\r\nIt should be `false` initial to make it useable. If its true, and I use it in a `\u003Cinput type=\"text\" :disabled=\"pending\"/>`, the input field is disabled on first visible moment, which's a wrong ux.\r\n\r\n### Additional context\r\n\r\nI tested vueUse's isFetching property in a empty vue environment and it is false per default.\r\n\r\n```\r\nimport { useFetch } from \"@vueuse/core\";\r\n\r\nconst { isFetching, execute } = useFetch(\r\n \"https://api.chucknorris.io/jokes/random\",\r\n {\r\n immediate: false,\r\n }\r\n);\r\n\r\n// isFetching.value === false\r\n```\r\n\r\n### Logs\r\n\r\n_No response_",[2965,2968],{"name":2966,"color":2967},"3.x","29bc7f",{"name":2969,"color":2970},"pending triage","E99695",19333,"UseFetch pending is initial true with {immediate: false} option","2023-11-15T20:53:47Z","https://github.com/nuxt/nuxt/issues/19333",0.64641494,{"description":2977,"labels":2978,"number":2981,"owner":2877,"repository":2877,"state":2916,"title":2982,"updated_at":2983,"url":2984,"score":2985},"### Environment\n\n- Operating System: `Linux`\r\n- Node Version: `v16.17.1`\r\n- Nuxt Version: `3.2.2`\r\n- Nitro Version: `2.2.2`\r\n- Package Manager: `npm@8.15.0`\r\n- Builder: `vite`\r\n- User Config: `runtimeConfig`, `modules`, `css`, `app`, `experimental`, `imports`, `nitro`, `typescript`\r\n- Runtime Modules: `@pinia/nuxt@0.4.7`, `@nuxtjs/tailwindcss@6.4.1`\r\n- Build Modules: \n\n### Reproduction\n\n\r\n```\r\n// before refresh call asyncData a pending must be false\r\nconst { pending: isLoadingOne, refresh: fetchOne } = useFetch('https://jsonplaceholder.typicode.com/todos/1', { immediate: false });\r\n\r\n// before refresh call asyncData a pending must be false | perhaps a controversial case\r\nconst { pending: isLoadingTwo, refresh: fetchTwo } = await useFetch('https://jsonplaceholder.typicode.com/todos/2', { immediate: false });\r\n```\r\n\r\nSee full code: https://stackblitz.com/edit/nuxt-starter-9uxzmd?file=app.vue\n\n### Describe the bug\n\nUntil the request is forcibly invoked, it is assumed that the waiting status should be false.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2979,2980],{"name":2966,"color":2967},{"name":2969,"color":2970},19218,"`useFetch/useAsyncData`: BUG: when `immediate: false`, then `pending` is `true` before call `execute/refresh` (must to be false)","2023-12-20T16:49:10Z","https://github.com/nuxt/nuxt/issues/19218",0.64952004,["Reactive",2987],{},["Set"],["ShallowReactive",2990],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$feqngyFA0ObB2qMxzOqqr_E5eSbQl6QZSySpkBYXwhQs":-1},"/nuxt/ui/3602"]