\n\n### Expected\n\n\u003Cimg width=\"1186\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/61bf37ec-4b5b-46dc-9e0f-cd9cd38b79c4\" />\n\n\n\n\nWould appreciate any guidance on achieving proper column alignment between UTable and the total row!",[2020],{"name":2021,"color":2022},"question","d876e3",3409,"How to implement fixed footer row in UTable?","2025-03-12T19:15:29Z","https://github.com/nuxt/ui/issues/3409",0.7195674,{"description":2029,"labels":2030,"number":2034,"owner":1997,"repository":1998,"state":1999,"title":2035,"updated_at":2036,"url":2037,"score":2038},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v22.14.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.22.1\n- Nitro Version: 2.10.4\n- Package Manager: npm@11.2.0\n- Builder: -\n- User Config: typescript, ssr, nitro, runtimeConfig, css, extends, modules, devtools, routeRules, future, compatibilityDate, eslint\n- Runtime Modules: @nuxt/eslint@0.7.6, @nuxt/fonts@0.0.1, @vueuse/nuxt@12.7.0, @nuxt/ui@3.0.0-alpha.13, @nuxtjs/mdc@0.13.5, @pinia/nuxt@0.10.1\n- Build Modules: -\n------------------------------\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\n \u003Cdiv class=\"flex gap-2 flex-wrap grow justify-between items-baseline\">\n \u003Cdiv class=\"flex gap-2 items-baseline grow\">\n \u003Cdiv class=\"prose\">\n \u003Ch1>\n XXX\n \u003C/h1>\n \u003C/div>\n \u003Cspan>XXX\u003C/span>\n \u003C/div>\n\n \u003Cdiv class=\"flex gap-2 items-baseline grow\">\n\n \u003CUButton icon=\"i-mdi:close-circle-outline\">XXX\u003C/UButton>\n \u003CUModal>\n \u003CUButton>XXX\u003C/UButton>\n \u003C/UModal>\n \u003CUCheckbox label=\"XXX\">\u003C/UCheckbox>\n \u003CUInput :model-value=\"'XXX'\">\u003C/UInput>\n \u003C/div>\n \u003C/div>\n\n### Description\n\n\n\nButton baseline is on icon and checkbox \n\n### Additional context\n\nflex workaround is not applicable for Checkbox and I want to align button with H1 and span.\n\n### Logs\n\n```shell-script\n\n```",[2031,2032,2033],{"name":1985,"color":1986},{"name":1988,"color":1989},{"name":1994,"color":1995},3466,"Button and Checkbox baseline","2025-03-06T09:34:44Z","https://github.com/nuxt/ui/issues/3466",0.729986,{"description":2040,"labels":2041,"number":2043,"owner":1997,"repository":1998,"state":2044,"title":2045,"updated_at":2046,"url":2047,"score":2048},"### For what version of Nuxt UI are you suggesting this?\n\nv2.x\n\n### Description\n\nThe config of the divider component allows to define types:\n\n```\ntype: {\n solid: 'border-solid',\n dotted: 'border-dotted',\n dashed: 'border-dashed',\n},\n```\n\nHowever, the solid type is set by default and can only be changed per Divider component, not globally via config. It would be great to be able to set a custom default type like so:\n\n```\ndefault: {\n border: {\n type: 'dotted',\n },\n},\n```\n\n### Additional context\n\n_No response_",[2042],{"name":2008,"color":2009},2398,"closed","Define default type for Divider","2024-10-19T12:19:23Z","https://github.com/nuxt/ui/issues/2398",0.674427,{"description":2050,"labels":2051,"number":2054,"owner":1997,"repository":1998,"state":2044,"title":2055,"updated_at":2056,"url":2057,"score":2058},"",[2052,2053],{"name":1985,"color":1986},{"name":1988,"color":1989},2338,"[Tabs] Height shifts of 1px between `pill` and `link` variants","2024-10-28T09:49:02Z","https://github.com/nuxt/ui/issues/2338",0.69073296,{"description":2060,"labels":2061,"number":2062,"owner":1997,"repository":2063,"state":2044,"title":2064,"updated_at":2065,"url":2066,"score":2067},"Hello everyone,\r\n\r\nI have a few questions about Nuxt test-utils.\r\n\r\nMy situation:\r\n\r\n- I have a Vue.js project with Vue test-utils;\r\n- I have a Nuxt.js project where I would like to add testing;\r\n\r\nI'm looking into different options for libraries to test my Nuxt.js project. Ideally, I would like to have something very similar to Vue test-utils, in order to avoid headaches when working on both projects. Nuxt test-utils seems like an interesting option, but I was wondering what are its advantages compared to just using Vue test-utils? Thanks!",[],451,"test-utils","Question: Vue test-utils vs Nuxt test-utils","2023-12-02T00:13:11Z","https://github.com/nuxt/test-utils/issues/451",0.70937747,{"description":2069,"labels":2070,"number":2074,"owner":1997,"repository":1998,"state":2044,"title":2075,"updated_at":2076,"url":2077,"score":2078},"### 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```",[2071,2072,2073],{"name":1985,"color":1986},{"name":1988,"color":1989},{"name":1994,"color":1995},3432,"UModal and useOverlay compatibility Issue","2025-03-11T13:57:03Z","https://github.com/nuxt/ui/issues/3432",0.72006845,{"description":2080,"labels":2081,"number":2082,"owner":1997,"repository":2083,"state":2044,"title":2084,"updated_at":2085,"url":2086,"score":2087},"Clicking the button close the dialog but nothing happens. Either on chrome or firefox.\n\nCome from https://github.com/nuxt/nuxt/issues/30827\n",[],1777,"nuxt.com","Ask AI doesn't work for me","2025-02-05T10:21:53Z","https://github.com/nuxt/nuxt.com/issues/1777",0.724689,{"description":2089,"labels":2090,"number":2093,"owner":1997,"repository":1998,"state":2044,"title":2094,"updated_at":2095,"url":2096,"score":2097},"### Description\n\nRight now there is no aria-* attributes in form inputs, that should be required to meet wcag aa:\n- associate form label elements with controls: id on the input and label-for in the label referencing the input id\n- aria-describedby for messages and errors on each form input\n- aria-invalid=\"true\" on each invalid form input (plus the aria-describedby referencing the error)\n- include form error recovery: via `Error alert, then focus`, `Errors on top` or `Inline errors`: I always use `Errors on top` + `Inline errors` (ui using inline errors)\n\nFor reference: https://webaim.org/techniques/formvalidation/\n\n\n### Additional context\n\n_No response_",[2091,2092],{"name":2008,"color":2009},{"name":1988,"color":1989},3111,"add a11y to form stuff","2025-01-25T13:14:07Z","https://github.com/nuxt/ui/issues/3111",0.7252674,["Reactive",2099],{},["Set"],["ShallowReactive",2102],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"opJVruesJnnGc_eIBdhZ7mk8y7C-23PTmEUfb7JOMqw":-1},"/nuxt/nuxt.com/1520"]