\n \u003CUButton\n variant=\"outline\"\n class=\"rounded\"\n label=\"Middle\"\n @click=\"open = false\"\n />\n \u003CUButton\n type=\"submit\"\n class=\"rounded\"\n label=\"Confirm\"\n color=\"primary\"\n @click=\"open = false\"\n />\n \u003C/div>\n \u003C/template>\n \u003C/UModal>\n \u003CUButton\n variant=\"outline\"\n color=\"neutral\"\n @click=\"\"\n >\n Other Button\n \u003C/UButton>\n \u003C/UButtonGroup>\n\u003C/template>\n```\n\n\u003Cimg width=\"362\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/da66f0d8-fc42-45a5-b1e1-d7214468b24a\" />\n\n\u003Cbr>\n\n\u003Cimg width=\"543\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/a50767ec-bea5-4c88-9b45-963f8e81e5df\" />\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2004,2007],{"name":2005,"color":2006},"bug","d73a4a",{"name":2008,"color":2009},"v3","49DCB8",2978,"ui","closed","The button styles in UModal body should not be affected by UButtonGroup.","2025-02-07T15:32:58Z","https://github.com/nuxt/ui/issues/2978",0.667188,{"description":2018,"labels":2019,"number":2022,"owner":1985,"repository":2011,"state":2012,"title":2023,"updated_at":2024,"url":2025,"score":2026},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v22.13.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: bun@1.2.2\n- Builder: -\n- User Config: compatibilityDate, devtools, runtimeConfig, nitro, routeRules, modules, supabase, site, feed, sitemap, robots, schemaOrg, image\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.12, @nuxtjs/supabase@1.4.6, @vueuse/nuxt@12.5.0, @nuxt/image@1.9.0, @nuxthub/core@0.8.15, @nuxtjs/sitemap@7.2.4, nuxt-module-feed@1.1.4, @nuxtjs/robots@5.2.2, nuxt-schema-org@4.1.1, nuxt-link-checker@4.1.0\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.12\n\n### Reproduction\n\n```vue\n\u003CUModal\n :ui=\"{\n title: 'sr-only',\n description: 'sr-only',\n }\"\n :title=\"will not work\"\n :description=\"will not work\">\n \u003Ctemplate #content>\n \u003Cp>anything\u003C/p>\n \u003C/template>\n\u003C/UModal>\n```\n\n### Description\n\nNot having a title or description set for the modal will throw the following RekaUI error:\n```\nPostingCard.vue:76 Warning: `DialogContent` requires a `DialogTitle` for the component to be accessible for screen reader users.\n\nIf you want to hide the `DialogTitle`, you can wrap it with our VisuallyHidden component.\n\nWarning: Missing `Description` or `aria-describedby=\"undefined\"` for DialogContent.\n```\n\nThis is expected.\n\nThe problem is when you use the `content` slot of `UModal`, you can't set the title or description, either through props or by using the `title` or `description` slot.\n\nIt would be nice if setting the title and description slots/props while using the content still applies them but automatically applies `sr-only`.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2020,2021],{"name":2005,"color":2006},{"name":2008,"color":2009},3267,"Modal content slot causes accessibility issues","2025-02-21T10:49:04Z","https://github.com/nuxt/ui/issues/3267",0.69163316,{"description":2028,"labels":2029,"number":2032,"owner":1985,"repository":1986,"state":2012,"title":2033,"updated_at":2034,"url":2035,"score":2036},"",[2030],{"name":2005,"color":2031},"ff281a",120,"Fix file fetch in project content editor","2022-03-07T14:15:00Z","https://github.com/nuxt/nuxt.com/issues/120",0.7183602,{"description":2038,"labels":2039,"number":2045,"owner":1985,"repository":2011,"state":2012,"title":2046,"updated_at":2047,"url":2048,"score":2049},"### Environment\n\nlatest\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.13\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/gifted-moon-ms65xm\n\n### Description\n\nhovering over a open drop down item in a drawer results in a recursion error.\n\n### Additional context\n\n```vue\n\u003Cscript setup lang=\"ts\">\nconst items = ref([\n {\n label: 'hover me for a recursion error',\n },\n])\n\u003C/script>\n\n\n\u003Ctemplate>\n \u003CUDrawer>\n \u003CUButton label=\"Open Drawer\"/>\n \u003Ctemplate #content>\n \u003CUDropdownMenu\n :items=\"items\"\n >\n \u003CUButton label=\"Open Drop down\"/>\n \u003C/UDropdownMenu>\n \u003C/template>\n \u003C/UDrawer>\n\u003C/template>\n```\n\n### Logs\n\n```shell-script\nUncaught InternalError: too much recursion\n NuxtJS 5\n focus\n handleFocusOut\n ct\n f\n focus\n```",[2040,2041,2042],{"name":2005,"color":2006},{"name":2008,"color":2009},{"name":2043,"color":2044},"reka-ui","56d799",3357,"Cant put dropdown inside drawer","2025-04-08T19:49:57Z","https://github.com/nuxt/ui/issues/3357",0.71916044,{"description":2051,"labels":2052,"number":2058,"owner":1985,"repository":2011,"state":2012,"title":2059,"updated_at":2060,"url":2061,"score":2062},"### Environment\n\n- Browser: Chrome\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/adoring-voice-d9qkcm?file=%2Fapp%2Fapp.vue&workspaceId=ws_5Su8Z3T5M7yHmVJXK9f8ix\n\n### Description\n\nThe tooltip allows to control it's open state via `v-model:open`. In this case it shouldn't automatically open on hover or at least have an option to disable it, as we trigger it manually.\n\nIn the reproduction we can see that it works, if the inout is focused via keyboard, but as soon as we focus it via mouse, the tooltip won't work.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2053,2054,2055],{"name":2005,"color":2006},{"name":2008,"color":2009},{"name":2056,"color":2057},"triage","ffffff",3774,"Tooltip: do not open / close on controlled state","2025-04-02T15:24:42Z","https://github.com/nuxt/ui/issues/3774",0.72275096,{"description":2064,"labels":2065,"number":2073,"owner":1985,"repository":2011,"state":2012,"title":2074,"updated_at":2075,"url":2076,"score":2077},"### Description\n\nThanks to the team for the wonderful UI library. I purchased a license for nuxt/ui-pro, but encountered an activation problem - after paying and receiving the key, I could not [activate](https://ui3.nuxt.dev/pro/activate) it, the system gave an error. `[POST] \"https://api.nuxtlabs.com/ui-pro/activate\": \u003Cno response> Failed to fetch`",[2066,2069,2070],{"name":2067,"color":2068},"question","d876e3",{"name":2008,"color":2009},{"name":2071,"color":2072},"pro","5BD3CB",3341,"License key activation error","2025-02-17T12:02:07Z","https://github.com/nuxt/ui/issues/3341",0.72533756,{"description":2079,"labels":2080,"number":2085,"owner":1985,"repository":2011,"state":2012,"title":2086,"updated_at":2087,"url":2088,"score":2089},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.13.0\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.7\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: modules, compatibilityDate, devtools, css, ui, devServer, future, telemetry, hooks, eslint\n- Runtime Modules: @nuxt/eslint@0.6.2, @nuxt/ui-pro@3.0.1, nuxt-jsonld@2.1.0, @pinia/nuxt@0.10.1\n- Build Modules: -\n\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nNuxt v3.16.1\nui-pro v3.0.1\n\n### Reproduction\n\nWhen I add the following to my nuxt.config.ts:\n\n```ts\n{\n ui: {\n colorMode: false\n }\n}\n```\n\n...then `npx nuxi typecheck` fails with 8 errors.\n\n```\n[...snip]\nnode_modules/@nuxt/ui-pro/dist/runtime/vue/components/ColorModeButton.vue:18:24 - error TS2305: Module '\"#imports\"' has no exported member 'useColorMode'.\n\n18 import { useAppConfig, useColorMode } from '#imports'\n ~~~~~~~~~~~~\n\nnode_modules/@nuxt/ui-pro/dist/runtime/vue/components/ColorModeSelect.vue:10:24 - error TS2305: Module '\"#imports\"' has no exported member 'useColorMode'.\n\n10 import { useAppConfig, useColorMode } from '#imports'\n ~~~~~~~~~~~~\n\nnode_modules/@nuxt/ui-pro/dist/runtime/vue/components/ColorModeSwitch.vue:10:24 - error TS2305: Module '\"#imports\"' has no exported member 'useColorMode'.\n\n10 import { useAppConfig, useColorMode } from '#imports'\n ~~~~~~~~~~~~\n\n\nFound 8 errors in 8 files.\n\nErrors Files\n 1 node_modules/@nuxt/ui-pro/dist/runtime/components/color-mode/ColorModeButton.vue:18\n 1 node_modules/@nuxt/ui-pro/dist/runtime/components/color-mode/ColorModeSelect.vue:10\n 1 node_modules/@nuxt/ui-pro/dist/runtime/components/color-mode/ColorModeSwitch.vue:10\n 1 node_modules/@nuxt/ui-pro/dist/runtime/components/content/ContentSearch.vue:89\n 1 node_modules/@nuxt/ui-pro/dist/runtime/components/DashboardSearch.vue:57\n 1 node_modules/@nuxt/ui-pro/dist/runtime/vue/components/ColorModeButton.vue:18\n 1 node_modules/@nuxt/ui-pro/dist/runtime/vue/components/ColorModeSelect.vue:10\n 1 node_modules/@nuxt/ui-pro/dist/runtime/vue/components/ColorModeSwitch.vue:10\n\n ERROR Process exited with non-zero status (2)\n```\n\n### Description\n\nI think that there probably needs to be a stub export set up in all cases? Or these files should not be gathered by the typechecking script?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2081,2082,2083,2084],{"name":2005,"color":2006},{"name":2008,"color":2009},{"name":2071,"color":2072},{"name":2056,"color":2057},3657,"Setting ui.colorMode = false breaks nuxi typecheck","2025-03-27T20:54:57Z","https://github.com/nuxt/ui/issues/3657",0.7261112,{"description":2091,"labels":2092,"number":2099,"owner":1985,"repository":1985,"state":2012,"title":2100,"updated_at":2101,"url":2102,"score":2103},"### Environment\r\n\r\n```\r\nNuxi 3.3.3\r\n\r\nRootDir: /project/home/benjaminrobinet/workspace\r\nNuxt project info:\r\n\r\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v16.17.0`\r\n- Nuxt Version: `3.3.3`\r\n- Nitro Version: `2.3.2`\r\n- Package Manager: `pnpm@7.1.0`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\r\n```\r\n\r\n### Reproduction\r\n\r\nhttps://codesandbox.io/p/sandbox/reactivity-issue-dlxt09\r\n\r\nThe page `index.vue` is mutating the reactive object, and the component `StateComponent.vue` is displaying the value and using it to apply a CSS class using a computed.\r\n\r\n### Describe the bug\r\n\r\nHere we have a useState method that is mutated to another value on the setup of a page. The template reacts well when using `{{ stateValue }}`, but not in computed, template binding, etc...\r\n\r\nI added a button to mutate the state on a nextTick, and it works as expected. That's probably not a useState issue, as I have the same issue with Pinia.\r\n\r\nEDIT: On HMR, it works fine.\r\n\r\nThe expected behavior is that everything should be correctly reactive to that reactive object.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2093,2096],{"name":2094,"color":2095},"3.x","29bc7f",{"name":2097,"color":2098},"pending triage","E99695",20130,"Reactivity / hydratation issue on render with reactive object","2023-04-07T13:50:33Z","https://github.com/nuxt/nuxt/issues/20130",0.7264256,["Reactive",2105],{},["Set"],["ShallowReactive",2108],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"pgK4AJ9h-JYRuvtRAg0-lVgUJT5YJRhMFw-BA5DkfBA":-1},"/nuxt/nuxt.com/1136"]