\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```",[1998,2001,2004],{"name":1999,"color":2000},"bug","d73a4a",{"name":2002,"color":2003},"v3","49DCB8",{"name":2005,"color":2006},"triage","ffffff",3607,"ui","Background-Color for UTable","2025-03-18T15:08:25Z","https://github.com/nuxt/ui/issues/3607",0.6772812,{"description":2014,"labels":2015,"number":2021,"owner":1988,"repository":2008,"state":1990,"title":2022,"updated_at":2023,"url":2024,"score":2025},"### Description\n\nDescription:\nI am currently using the UTable component from Nuxt UI and have encountered a limitation regarding the customization of table headers. Specifically, I need to create a table with multi-row headers and the ability to merge columns using colspan. For example, the multi-row spanning column headers shown in the image.However, the current implementation of the UTable component does not seem to support this feature.\n\n\nCurrent Behavior:\n\nThe header property allows for custom content using the h function, but it is limited to single-column customization.\nThe available slots are primarily designed for single-column or specific row customization and do not support multi-column header customization.\nExpected Behavior:\n\nAbility to define headers that span multiple rows and columns.\nSupport for colspan and rowspan attributes in the header configuration to allow for more complex table layouts.\nEnhanced slot functionality to support multi-column header customization.\nUse Case:\nThis feature is essential for creating complex data tables where grouped headers are necessary for better data organization and presentation. It is particularly useful in scenarios where data needs to be categorized under broader headings.\n\nProposed Solution:\n\nIntroduce a mechanism in the UTable component to allow for multi-row and multi-column header definitions.\nProvide examples and documentation on how to implement these features using the existing API or through new enhancements.\nConsider expanding the slot functionality to support more complex header customizations.\nAdditional Context:\n\nThis feature is commonly supported in other table libraries and would greatly enhance the flexibility and usability of the UTable component in Nuxt UI.\nEnvironment:\n\nNuxt UI version: [3.0.0-alpha.12]\nNuxt version: [^3.15.4]\n\nRelated Issues Link:\nhttps://github.com/nuxt/ui/issues/1289#issuecomment-2652919275\nhttps://github.com/nuxt/ui/issues/1651\nhttps://github.com/nuxt/ui/issues/2053\n\nRelated Documentation Link:\nhttps://ui3.nuxt.dev/components/table\n\n### Additional context\n\n_No response_",[2016,2019,2020],{"name":2017,"color":2018},"enhancement","a2eeef",{"name":2002,"color":2003},{"name":2005,"color":2006},3296,"Support for Multi-Row and Colspan Headers in UTable Component","2025-02-14T09:56:42Z","https://github.com/nuxt/ui/issues/3296",0.68110317,{"description":2027,"labels":2028,"number":2034,"owner":1988,"repository":1989,"state":2035,"title":2036,"updated_at":2037,"url":2038,"score":2039},"Because `happy-dom` is not fully compatible with `jsdom`, we can't use, for example, `@testing-library/jest-dom` within the Nuxt environment. \r\nI suggest to add possibility to replace `happy-dom` with `jsdom`, `@happy-dom/jest-environment` etc.",[2029,2030,2033],{"name":2017,"color":2018},{"name":2031,"color":2032},"good first issue","7057ff",{"name":1985,"color":1986},553,"closed","Add option to replace `happy-dom` with `jsdom`","2023-12-02T00:37:13Z","https://github.com/nuxt/test-utils/issues/553",0.5962029,{"description":2041,"labels":2042,"number":2045,"owner":1988,"repository":2008,"state":2035,"title":2046,"updated_at":2047,"url":2048,"score":2049},"### Environment\n\nnuxt: 3.15.2\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha11\n\n### Reproduction\n\nself explanatory\n\n### Description\n\n\"Buttons do not have an accessible name\"\n\nComponent: USelect - Missing name/label for aria-label\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2043,2044],{"name":1999,"color":2000},{"name":2002,"color":2003},3130,"Missing Aria-Label on USelect Component","2025-02-21T11:26:36Z","https://github.com/nuxt/ui/issues/3130",0.65871316,{"description":2051,"labels":2052,"number":2056,"owner":1988,"repository":1988,"state":2035,"title":2057,"updated_at":2058,"url":2059,"score":2060},"### Environment\n\nStackblitz Sandbox\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-7wcdxads?file=app.vue,components%2FErrorContent.vue\n\n### Describe the bug\n\nI want to intercept errors within the component as much as possible, so that they only affect the current component and do not cause the entire page to crash. However, I tried the following three methods (all based on onErrorCaptured), and they work fine when useFetch is not used on the page. But once useFetch is used, the page directly returns a 500 status code, and I am unable to intercept the relevant errors to prevent the page from crashing.\n\nhttps://cn.vuejs.org/api/composition-api-lifecycle#onerrorcaptured\nhttps://nuxt.com/docs/getting-started/error-handling#vue-errors\nhttps://nuxt.com/docs/api/components/nuxt-error-boundary\n\nI hope there is a way to intercept errors within the component when using useFetch, so that it doesn't cause the entire page to display a 500 error, thanks.\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2053],{"name":2054,"color":2055},"pending triage","E99695",30917,"fetchData causes onErrorCaptured to be unable to capture errors","2025-02-22T20:46:13Z","https://github.com/nuxt/nuxt/issues/30917",0.6968419,{"description":2062,"labels":2063,"number":2074,"owner":1988,"repository":1988,"state":2035,"title":2075,"updated_at":2076,"url":2077,"score":2078},"### Environment\r\n\r\nnuxt: 3.8.2\r\n\r\n### Reproduction\r\n\r\n```ts\r\nconst newOptions: UseFetchOptions\u003CT> = {\r\n baseURL: BASE_URL,\r\n method,\r\n // headers: { ...normalParams },\r\n onRequest ({ options }) {\r\n options.headers = {\r\n ...optionsHeader,\r\n 'Content-Type': 'application/json'\r\n }\r\n },\r\n async onResponse ({ response }) {\r\n const responseData = typeof response._data === 'string' ? JSON.parse(response._data) : response._data\r\n const { code } = responseData\r\n if (code === RESPOND.SUCCESS) {\r\n return response._data\r\n } else if (NOT_FOUND_CODES.includes(code)) {\r\n navigateTo('/404/')\r\n return Promise.reject(response._data)\r\n } else {\r\n if (LOGOUT_CODES.includes(code)) {\r\n user.clearUserInfo()\r\n }\r\n return response._data\r\n }\r\n },\r\n onResponseError ({ response }) {\r\n return response?._data ?? null\r\n },\r\n ...options\r\n }\r\n\r\nuseFetch(url, newOptions)\r\n .then((res) => {\r\n if (typeof res.data.value === 'string') {\r\n resolve(JSON.parse(res.data.value))\r\n } else {\r\n resolve(res.data.value)\r\n }\r\n })\r\n .catch((error) => {\r\n reject(error)\r\n })\r\n```\r\n\r\n### Describe the bug\r\n\r\n\r\n\r\n\r\nthe same request in production environment,status is error and data is null, but in development environment i got data and status is success.\r\nonResponse and onResponseError is not executed.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2064,2067,2068,2071],{"name":2065,"color":2066},"3.x","29bc7f",{"name":2054,"color":2055},{"name":2069,"color":2070},"needs reproduction","FBCA04",{"name":2072,"color":2073},"closed-by-bot","ededed",25032,"useFetch request status is error, data is null","2024-01-11T01:49:31Z","https://github.com/nuxt/nuxt/issues/25032",0.69706213,{"description":2080,"labels":2081,"number":2084,"owner":1988,"repository":1988,"state":2035,"title":2085,"updated_at":2086,"url":2087,"score":2088},"### Environment\n\n- Node Version: v18.18.0\r\n- Nuxt 3.8.0\r\n- Nitro 2.7.2\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-jgqfhc?file=pages%2Findex.vue\n\n### Describe the bug\n\nIf use useFetch and receive a response of 404 500 ... After that, change the web page. and return to the original page.\r\nuseFetch will not resend the request and will continue to use the same one it received before. But if refresh the website, useFetch will work normally.\n\n### Additional context\n\nThis is caching of useFecth? How do I handle it?\n\n### Logs\n\n_No response_",[2082,2083],{"name":2065,"color":2066},{"name":2054,"color":2055},24008,"useFetch cache Error response and never load it again","2023-10-28T17:16:54Z","https://github.com/nuxt/nuxt/issues/24008",0.69933504,{"description":2090,"labels":2091,"number":2094,"owner":1988,"repository":2008,"state":2035,"title":2095,"updated_at":2096,"url":2097,"score":2098},"### Environment\n\n- Operating System: `Windows 11`\n- Node Version: `v20.18.0`\n- Nuxt Version: `4 (nightly release), 4.0.0-28826831.b619b35e`\n- Nitro Version: `2.6.3`\n- CLI Version: 3.15.1-20241022-160139-45801c0\n- Nuxt Version: 4.0.0-28826831.b619b35e\n- Package Manager: `npm@10.8.0 or bun@1.1.33`\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.6\n- Build Modules: -\n\n\n### Version\n\nv3.0.0-alpha.6\n\n### Reproduction\n\nhttps://github.com/kashiarain/nuxt4-nuxtui3-repro\n\n### Description\n\nI am experiencing issues with NuxtUI3 alpha when using it alongside the nightly release of Nuxt 4. When I try to run the development server, I encounter persistent loading and error messages.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2092,2093],{"name":1999,"color":2000},{"name":2002,"color":2003},2436,"NuxtUI3 Alpha Not Working with Nuxt 4 Nightly Release","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/2436",0.7082752,{"description":2100,"labels":2101,"number":2108,"owner":1988,"repository":1988,"state":2035,"title":2109,"updated_at":2110,"url":2111,"score":2112},"### Describe the feature\r\n\r\nWhen developing a rest API, it's considered good to use semantic status codes for different response types. So I do in my API routes:\r\n\r\n```ts\r\nimport { setResponseStatus } from 'h3'\r\n\r\nconst enum OperationResultKind {\r\n Created = 'Created',\r\n AlreadyExists = 'AlreadyExists',\r\n InvalidData = 'InvalidData',\r\n}\r\n\r\ntype OperationResult =\r\n| { kind: OperationResultKind.Created; user: User }\r\n| { kind: OperationResultKind.AlreadyExists }\r\n| { kind: OperationResultKind.InvalidData; problems: ValidationProblem[] }\r\n\r\nexport default defineEventHandler(event => {\r\n const unvalidatedData = readBody(event)\r\n const validationResult = // some validation stuff\r\n\r\n if (!validationResult.success) {\r\n setResponseStatus(event, 400)\r\n return { kind: OperationResultKind.InvalidData, problems: validationResult.problems }\r\n }\r\n\r\n const { data } = validationResult\r\n \r\n try {\r\n const insertedUser = await insertIntoDb(data)\r\n setResponseStatus(event, 203)\r\n return { kind: OperationResultKind.Created; user: insertedUser }\r\n } catch (e) {\r\n if (/* some error checking */) {\r\n setResponseStatus(event, 409)\r\n return { kind: OperationResultKind.AlreadyExists }\r\n }\r\n \r\n throw e\r\n }\r\n})\r\n```\r\n\r\nHowever, when fetching this route with `useFetch`, I end up with `InvalidData` and `AlreadyExists` errors being in the `error` ref. The thing is that these variants are some type of domain errors and I get no typings for them. The other thing is that the `data` ref is of type `OperationResult`, but it only may contain the `Created` variant so I end up using `as` to convert types which is not good. \r\n\r\nI could return only 2xx status codes to resolve this issue, but I might want to reuse this API in many different projects in the future so status codes must be semantic.\r\n\r\nI think that one option for resolving that may be adding some interceptor concept such as in Axios:\r\n```ts\r\naxios.get('/user/12345', {\r\n validateStatus: function (status) {\r\n return status \u003C 500; // Resolve only if the status code is less than 500\r\n }\r\n})\r\n```\r\n\r\nAlso one would want to use this validation interceptor globally, so it's worth adding this to `nuxt.config.ts`.\r\n\r\n### Additional information\r\n\r\n- [X] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2102,2104,2105],{"name":2017,"color":2103},"8DEF37",{"name":2065,"color":2066},{"name":2106,"color":2107},"upstream","E8A36D",18713,"Add an option to `useFetch` to not consider non-5xx status codes as errors","2023-10-22T09:04:12Z","https://github.com/nuxt/nuxt/issues/18713",0.71095324,["Reactive",2114],{},["Set"],["ShallowReactive",2117],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"GsX6YyRVEEGV7DBpgX1KbAFR_Ef6W5NNK6GMBYmurDE":-1},"/nuxt/nuxt.com/526"]