\n```\n\nWould it be relevant to add a global attribute to components like Button, Badge, etc., to force their appearance in dark (or light) mode, regardless of the global setting? This would ensure better visual consistency when these elements are placed on a colored background (e.g., `UPageCTA` with `solid` variant).\n\n### Additional context\n\n_No response_",[2039,2040,2041],{"name":2017,"color":2018},{"name":1988,"color":1989},{"name":1991,"color":1992},3307,"Better handling of `UButton`, `UBadge`, … colors on colored backgrounds","2025-02-13T19:05:27Z","https://github.com/nuxt/ui/issues/3307",0.69026226,{"description":2048,"labels":2049,"number":2052,"owner":1994,"repository":1995,"state":2053,"title":2054,"updated_at":2055,"url":2056,"score":2057},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.4.0\n- Nuxt Version: 3.14.159\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.13.2\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.8\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.8\n\n### Reproduction\n\n-\n\n### Description\n\nDefault classes of container in [docs](https://ui3.nuxt.dev/components/container#theme) is:\n```ts\nexport default defineAppConfig({\n ui: {\n container: {\n base: 'max-w-[var(--ui-container)] mx-auto px-4 sm:px-6 lg:px-8'\n }\n }\n})\n```\n**But no one of classes except `mx-auto` is not was created.**\nI change `--ui-container` variable like in [docs](https://ui3.nuxt.dev/getting-started/theme#container):\n```css\n/** app.css */\n\n@import 'tailwindcss';\n@import '@nuxt/ui';\n\n@theme {\n --container-xl: 1280px;\n}\n\n:root {\n --ui-container: var(--container-xl);\n}\n```\nAs result, container classes is `max-w-7xl mx-auto px-4 sm:px-6 lg:px-8` and still not was created, except `mx-auto`.\n\nBut if i create `app.config.ts`:\n```ts\nexport default defineAppConfig({\n ui: {\n container: {\n base: 'max-w-[var(--ui-container)] mx-auto px-4 sm:px-6 lg:px-8'\n }\n }\n})\n```\nAll is ok, width and other classes are created and applying.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2050,2051],{"name":1985,"color":1986},{"name":1988,"color":1989},2655,"closed","Classes of container component are not working properly","2024-11-16T13:13:33Z","https://github.com/nuxt/ui/issues/2655",0.6634873,{"description":2059,"labels":2060,"number":2066,"owner":1994,"repository":1995,"state":2053,"title":2067,"updated_at":2068,"url":2069,"score":2070},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.18.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.16.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.12.3\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/image@1.8.1, @nuxt/content@2.13.4, @nuxthq/studio@1.1.2, @nuxt/ui-pro@3.0.0-alpha.10, @nuxtjs/plausible@1.2.0, @nuxtjs/seo@2.0.2, @vueuse/nuxt@12.0.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0.alpha10\n\n### Reproduction\n\nhttps://ui3.nuxt.dev/components/button#loading (example with `loading-auto`)\n\n### Description\n\nWhen using a `UIButton` component with an `@click` event, the cursor does not change to `cursor-pointer`, which may confuse users about the button's clickability.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2061,2062,2065],{"name":1985,"color":1986},{"name":2063,"color":2064},"duplicate","cfd3d7",{"name":1988,"color":1989},2940,"`cursor-pointer` is missing on `UButton` with an `@click` event","2025-04-02T09:37:12Z","https://github.com/nuxt/ui/issues/2940",0.6661868,{"description":2072,"labels":2073,"number":2076,"owner":1994,"repository":1995,"state":2053,"title":2077,"updated_at":2078,"url":2079,"score":2080},"### Description\n\ni noticed that NUXT UI / NUXT UI PRO were refactored to use tailwind's new version 3 stuff + radix...\n\ni just went to the tailwind docs today and it looks like they just skipped right past their new version 3 and went to version 4...\n\nany ideas how this effects NUXT UI/PRO? \n\nMy undersanding is that version 3->4 means it was a semver breaking change?",[2074,2075],{"name":2005,"color":2006},{"name":1988,"color":1989},3167,"tailwind version 4..?","2025-01-24T10:17:32Z","https://github.com/nuxt/ui/issues/3167",0.6668172,{"labels":2082,"number":2089,"owner":1994,"repository":1994,"state":2053,"title":2090,"updated_at":2091,"url":2092,"score":2093},[2083,2086],{"name":2084,"color":2085},"3.x","29bc7f",{"name":2087,"color":2088},"pending triage","E99695",14489,"VueUse `useMounted` results in \"onMounted is called when there is no active component instance\" during SSR in production mode","2023-08-30T19:48:13Z","https://github.com/nuxt/nuxt/issues/14489",0.668076,{"labels":2095,"number":2101,"owner":1994,"repository":1994,"state":2053,"title":2102,"updated_at":2103,"url":2104,"score":2105},[2096,2097,2098],{"name":2084,"color":2085},{"name":1985,"color":1986},{"name":2099,"color":2100},"upstream","E8A36D",12182,"ReferenceError: window is not defined","2023-01-19T15:59:20Z","https://github.com/nuxt/nuxt/issues/12182",0.668667,["Reactive",2107],{},["Set"],["ShallowReactive",2110],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"oneSjpNUQ5d50u6iBiRL5j0zPc4jc5EfxPl4g7p474U":-1},"/nuxt/ui/3283"]