\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_",[3153,3156],{"name":3154,"color":3155},"enhancement","a2eeef",{"name":3157,"color":3158},"v3","49DCB8",3307,"ui","Better handling of `UButton`, `UBadge`, … colors on colored backgrounds","2025-08-25T13:20:01Z","https://github.com/nuxt/ui/issues/3307",0.78726864,{"description":3166,"labels":3167,"number":3175,"owner":3143,"repository":3160,"state":3145,"title":3176,"updated_at":3177,"url":3178,"score":3179},"### Environment\n\n```\n- Node Version: v20.12.0\n- Nuxt Version: 3.17.3\n- Runtime Modules: @nuxt/ui@3.3.3\n- Browser: Chromium 136 (windows)\n```\n\n#### Version\n\nv3.3.3\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/mutable-frog-xc2v8p\n\n### Description\n\nHello Nuxt Ui team!\n\nI noticed two issues with `USelect` & `USelectMenu`:\n\n1. **Input autofocus issue:** \n When typing in the input, opening the select causes the input to lose focus. Setting `:autofocus=\"false\"` has no effect, the select is still focused when opened.\n\n2. **Body lock issue:** \n Setting `:content=\"{ bodyLock: false }\"` does not prevent the body from being locked. The CSS property `pointer-events: default;` is still applied on the body.\n\nIn the case of an autocomplete, this prevents continuing to type in the input while still displaying suggested results.\n\nThanks for your help!\n",[3168,3171,3172],{"name":3169,"color":3170},"bug","d73a4a",{"name":3157,"color":3158},{"name":3173,"color":3174},"triage","ffffff",4956,"`USelect` & `USelectMenu` setting :autofocus to false or :content `bodyLock` to false have no effect","2025-09-12T12:07:19Z","https://github.com/nuxt/ui/issues/4956",0.7932085,{"description":3181,"labels":3182,"number":3186,"owner":3143,"repository":3187,"state":3145,"title":3188,"updated_at":3189,"url":3190,"score":3191},"Im trying to use country-icons dynamically based on input, but Im having issues.\n\n```\n\u003Cscript setup lang=\"ts\">\nimport { Icon } from '#components'\n\nconst props = defineProps\u003C{\n country: string\n}>()\n\nconst icon = computed(() => {\n const icon = props?.country.toLowerCase()\n if (icon == 'northern ireland') {\n return 'ireland'\n }\n return icon\n})\nconst FlagIcon = h(Icon, { name: 'twemoji:flag-' + icon.value, size: 18 })\n\n\u003C/script>\n\u003Ctemplate>\n \u003CFlagIcon />\n\u003C/template>\n```\n\nThis is working when loading the page SSR, but navigating to the page results in errors like this:\n`DR5f3n0Z.js:52 [Icon] failed to load icon 'twemoji:flag-hungary'`\n\nHow can I create the icon names dynamically?",[3183],{"name":3184,"color":3185},"need-repro","A50BA3",321,"icon","Dynamic icon name","2024-12-12T08:54:20Z","https://github.com/nuxt/icon/issues/321",0.79441696,{"description":3193,"labels":3194,"number":3195,"owner":3143,"repository":3187,"state":3145,"title":3196,"updated_at":3197,"url":3198,"score":3199},"According to the [Vue-Iconify Docs](https://iconify.design/docs/icon-components/vue/transform.html#rotation) one can pass a `rotate` and `flip` Prop to transform the Icon, to display it in different orientations.\r\n\r\n```vue\r\n\u003Ctemplate>\r\n \u003CIcon name=\"ic:round-double-arrow\" size=\"26\" :rotate=\"flip && '2'\" />\r\n\u003C/template>\r\n\r\n\u003Cscript setup lang=\"ts\">\r\nconst flip = ref(false);\r\n\u003C/script>\r\n```\r\n\r\nWhile this works fine with nuxt-icon during development, it breaks in a Prod build. The transformations no longer get applied.\r\n\r\nIt would be great if nuxt-icon could also support these props, if possible. I'm open to help with this issue if someone could give me some pointers where to start.",[],138,"[Feature Request] Support Iconify Transformations","2024-03-15T09:15:14Z","https://github.com/nuxt/icon/issues/138",0.79535306,{"description":3201,"labels":3202,"number":3206,"owner":3143,"repository":3160,"state":3207,"title":3208,"updated_at":3209,"url":3210,"score":3211},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.11.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.22.2\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.2.4\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, css\n- Runtime Modules: @nuxt/ui@3.0.0-beta.2\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.0-beta.2\n\n### Reproduction\n\nHere's a demo (https://codesandbox.io/p/devbox/nuxtui3-bug-3432-sphrpl)\n\n**index.vue**\n```\n\u003Ctemplate>\n \u003CUContainer>\n \u003CFooModal @some-action=\"fnHandleAction\" /> \u003Cbr />\n \u003CUButton @click=\"fnOpenModal\">Open FooModal from code\u003C/UButton>\n \u003C/UContainer>\n\u003C/template>\n\n\u003Cscript lang=\"ts\" setup>\n import { FooModal } from '#components';\n\n const overlay = useOverlay();\n\n const foo = overlay.create(FooModal);\n\n const fnOpenModal = async () => {\n foo.open();\n };\n\n const fnHandleAction = (action) => {\n console.log(\"Handle FooModal action: \", action);\n };\n\u003C/script>\n```\n\n**FooModal**\n```\n\u003Ctemplate>\n \u003CUModal v-model:open=\"open\" title=\"Foobar\">\n \u003CUButton label=\"Open FooModal from modal\" color=\"neutral\" variant=\"subtle\" />\n\n \u003Ctemplate #body>\n \u003CUButton @click=\"click()\" >Submit\u003C/UButton>\n \u003C/template>\n \u003C/UModal>\n\u003C/template>\n\n\u003Cscript lang=\"ts\" setup>\n const open = ref(false);\n\n const emits = defineEmits(['some-action']);\n\n const click = () => {\n console.log(\"clicked from inside the modal\");\n emits('some-action', 'closing'); //emits does not work if Modal opened using useOverlay.\n open.value = false; //closing modal does not work if Modal opened using useOverlay.\n };\n\u003C/script>\n```\n\n### Description\n\nHello Nuxt UI team,\n\nThank you for providing a high-quality UI library. I truly appreciate the effort you put into creating and maintaining it.\n\nI have encountered an issue while using `UModal` in my application. The modal is used to create and/or update database entries, and it needs to be opened in two different ways:\n\n1. Via a `UButton` that is always present on the screen (provided by the modal itself).\n2. Programmatically, through a link in a dropdown menu, using `useOverlay`.\n\nWhen the modal is opened using the first method, everything works as expected. However, when it is opened programmatically using the second method, the modal does not behave the same way. Specifically:\n\n- I am unable to trigger an `emit` to notify the parent component that the update was successful.\n- The modal does not close properly using the `open.value = false` technique.\n\nI am unsure if this behavior is intentional or a bug. I was under the impression that `UModal` and `useOverlay` should work seamlessly together and exhibit consistent behavior. Could you please confirm whether this is a valid concern?\n\nThank you for your time and attention to this matter. I look forward to your guidance.\n\n**Note**: You'll also notice that the button within the modal appears on the screen when opened using `useOverlay`. It would be helpful if it could be hidden automatically, but I believe this is something I can control easily. As such, I do not consider this to be a bug.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3203,3204,3205],{"name":3169,"color":3170},{"name":3157,"color":3158},{"name":3173,"color":3174},3432,"closed","UModal and useOverlay compatibility Issue","2025-03-11T13:57:03Z","https://github.com/nuxt/ui/issues/3432",0.77232474,{"description":3213,"labels":3214,"number":3219,"owner":3143,"repository":3160,"state":3207,"title":3220,"updated_at":3221,"url":3222,"score":3223},"### Description\n\nHi I have a mobile layout where I have a navbar stuck to the bottom of my screen which I want always visible. However when I use a UDrawer which comes out from the bottom it covers my navbar. I tried setting z-indexes in different places but it didn't seem to affect the UDrawer being overlayed on top of everything. \n\nWhich setting would be best to use to achieve this layout?",[3215,3218],{"name":3216,"color":3217},"question","d876e3",{"name":3157,"color":3158},4159,"Can I set the z-index of UDrawer?","2025-06-02T20:25:58Z","https://github.com/nuxt/ui/issues/4159",0.77554804,{"description":3225,"labels":3226,"number":3234,"owner":3143,"repository":3235,"state":3207,"title":3236,"updated_at":3237,"url":3238,"score":3239},"It would be preferable that the module use the protocol that is specified in either the vitest config or nuxt config.\r\n\r\nhttps://github.com/danielroe/nuxt-vitest/blob/178c11865380b0cadb4c4af196486ebba308d3a9/packages/nuxt-vitest/src/module.ts#L49\r\n\r\nThis is resulting in the dev tools being unable to show the proper page for the ui:\r\n\r\n\r\n",[3227,3228,3231],{"name":3169,"color":3170},{"name":3229,"color":3230},"good first issue","7057ff",{"name":3232,"color":3233},"vitest-environment","b60205",548,"test-utils","devtools iframe not able to run in https","2023-12-05T15:29:38Z","https://github.com/nuxt/test-utils/issues/548",0.7782434,{"description":3241,"labels":3242,"number":3246,"owner":3143,"repository":3160,"state":3207,"title":3247,"updated_at":3248,"url":3249,"score":3250},"### Description\n\nHello,\n\nI've spent the last couple of hours trying to implement right-click functionality on UTable rows. I've reviewed existing issues but couldn't find a solution that fits this need.\n\nWhat I want to achieve is to show a UContextMenu with actions related to the clicked row when the user right-clicks on it.\n\nCurrently, there is no way I could find to detect right-click events on individual rows along with their row data. If UTable had a #row slot or a dedicated @click.right event that provides the clicked row’s data, this would be easily achievable.\n\nIf there is any workaround or method to implement this right-click behavior on rows with access to row data, I would really appreciate if someone could share it.\n\nThank you!\n\n\n\n### Additional context\n\n_No response_",[3243,3244,3245],{"name":3154,"color":3155},{"name":3157,"color":3158},{"name":3173,"color":3174},4259,"Add support for @click.right event on UTable rows to enable context menus","2025-07-01T11:16:40Z","https://github.com/nuxt/ui/issues/4259",0.7845983,{"description":3252,"labels":3253,"number":3256,"owner":3143,"repository":3160,"state":3207,"title":3257,"updated_at":3258,"url":3259,"score":3260},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v20.16.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.22.1\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.8.1\n- Builder: -\n- User Config: devtools, compatibilityDate, modules, app, css, colorMode, svgSprite, future, imports, runtimeConfig, ssr\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.13, @nuxt/eslint@1.1.0, @nuxt/icon@1.10.3, @nuxtjs/svg-sprite@1.0.2, @nuxt/image@1.9.0, @vueuse/nuxt@12.7.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.0-alpha.13\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/stupefied-roentgen-y6tdsd\n\n### Description\n\n### Help Nuxt ui 3 table not reactive\n\nWhen I click the button, the table doesn't update. However, when I print the array object, the data is added, but the table still does not update\n\nhttps://codesandbox.io/p/devbox/stupefied-roentgen-y6tdsd\n\nThank you for help\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3254,3255],{"name":3169,"color":3170},{"name":3157,"color":3158},3377,"UI Table is not reactive","2025-02-27T21:19:42Z","https://github.com/nuxt/ui/issues/3377",0.7909015,["Reactive",3262],{},["Set"],["ShallowReactive",3265],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f8mfkgG2ZHx6kC_OPvpRw0sUx3MC1P77zPoGOVsedXKg":-1},"/nuxt/ui/4199"]