\n \u003C/UButton>\n\n \u003CUButton color=\"gray\" variant=\"ghost\" @click=\"continue\">\n Continue\n \u003CUIcon name=\"i-mdi-arrow-right-circle\" class=\"text-primary\" />\n \u003C/UButton>\n \u003C/div>\n \u003C/UCard>\n \u003C/UModal>\n```",[2015,2016],{"name":2002,"color":2003},{"name":2017,"color":2018},"stale","ededed",3187,"[V2] How to prevent button pre-selection on UModal?","2025-03-09T01:50:32Z","https://github.com/nuxt/ui/issues/3187",0.7956621,{"description":2025,"labels":2026,"number":2032,"owner":1991,"repository":1992,"state":2033,"title":2034,"updated_at":2035,"url":2036,"score":2037},"### Environment\n\nI don't use nuxt\n```\ndependencies:\n@nuxt/ui 3.0.1\n@tailwindcss/vite 4.0.15\n@vueuse/core 13.0.0\n@wxt-dev/storage 1.1.1\ncomctx 1.1.0\nswapy 1.0.5\ntailwindcss 4.0.15\nvue 3.5.13\n\ndevDependencies:\n@antfu/eslint-config 4.11.0\n@types/chrome 0.0.280\n@vitejs/plugin-vue-jsx 4.1.2\n@wxt-dev/module-vue 1.0.2\nprettier-eslint 16.3.0\ntypescript 5.6.3\nvue-tsc 2.2.8\nwxt 0.19.29\n```\n\n### Is this bug related to Nuxt or Vue?\n\nVue\n\n### Version\n\n3.0.1\n\n### Reproduction\n\n```tsx\nimport UIcon from \"@nuxt/ui/runtime/components/Icon.vue\";\nconst IconComp = defineComponent(() => {\n return () => (\n \u003CUIcon name=\"i-ant-design:account-book-filled\" />\n );\n});\n```\n\nhttps://codesandbox.io/p/devbox/dreamy-kepler-dqcx4s\n\n### Description\n\nWhen using the `UIcon` component in a JSX/TSX environment, it triggers a \"Maximum call stack size exceeded\" error. The issue appears to be caused by a circular reference in the `Icon.vue` component where it might be incorrectly referencing itself instead of the Nuxt UI icon.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2027,2030,2031],{"name":2028,"color":2029},"bug","d73a4a",{"name":2005,"color":2006},{"name":1988,"color":1989},3671,"closed","Maximum call stack size exceeded when using UIcon in JSX/TSX environment","2025-03-24T15:05:07Z","https://github.com/nuxt/ui/issues/3671",0.7305055,{"description":2039,"labels":2040,"number":2043,"owner":1991,"repository":1992,"state":2033,"title":2044,"updated_at":2045,"url":2046,"score":2047},"### Description\n\nI would like to propose the addition of Khmer language support (ភាសាខ្មែរ), which is the national language of Cambodia 🇰🇭. Adding Khmer will enhance accessibility for Khmer-speaking users and improve their experience when using the Nuxt/UI framework.\n\u003Ch1>Motivation\u003C/h1>\nCurrently, the absence of Khmer language support limits usability for a significant number of users who prefer to interact with applications in their native language. By including Khmer, we can:\n1. Broaden our user base in Cambodia and among Khmer-speaking communities worldwide.\n2. Improve user experience and engagement for Khmer-speaking developers and end-users.\n3. Align with our goal of inclusivity and accessibility in software development.\n\u003Ch1>Proposed Implementation\u003C/h1>\n1. Language Files: Create and include translation files for Khmer.\n2. Testing: Ensure that all components are correctly translated and function as expected in Khmer.\n3. Documentation: Update the documentation to reflect the new language support, including usage examples.\n\u003Ch1>Additional Notes\u003C/h1>\nThis is my first time to open a PR in Nuxt UI repo so if there are any specific guidelines or requirements for adding new languages, please let me know, and I would be happy to follow them.\nThank you for considering this request!\n\n### Additional context\n\n_No response_",[2041,2042],{"name":1985,"color":1986},{"name":2005,"color":2006},3118,"Request to Add Khmer Language Support","2025-01-25T13:14:14Z","https://github.com/nuxt/ui/issues/3118",0.7425466,{"description":2049,"labels":2050,"number":2053,"owner":1991,"repository":1992,"state":2033,"title":2054,"updated_at":2055,"url":2056,"score":2057},"### Environment\n\nOperating System: `Darwin`\nNode Version: `v22.11.0`\nNuxt Version: `3.14.1592`\nCLI Version: `3.16.0`\nNitro Version: `2.10.4`\nPackage Manager: `npm@10.9.0`\nBuilder: -\nUser Config: `default`\nRuntime Modules: `@nuxt/ui@3.0.0-alpha.9, @nuxt/eslint@0.7.2, @nuxt/image@1.8.1`\nBuild Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.9\n\n### Reproduction\n\nhttps://github.com/makvv4/nuxtui3-avatar-bug-reproduction\n\n### Description\n\nIn the markup we see the correct link to the image, but in the avatar component only a fallback is displayed.\nIn the Network tab, you can see that there are multiple requests made at the same time: one with the correct link, and another request links to the localhost.\n\nThe provider is located in `/providers/my-img-provider.ts`\nAnd config looks like:\n```javascript\nexport default defineNuxtConfig({\n devtools: { enabled: true },\n modules: ['@nuxt/ui', '@nuxt/eslint', '@nuxt/image'],\n css: ['~/assets/css/main.css'],\n\n future: {\n compatibilityVersion: 4,\n },\n\n compatibilityDate: '2024-11-27',\n\n image: {\n providers: {\n myImgProvider: {\n provider: '~~/providers/my-img-provider.ts',\n },\n },\n provider: 'myImgProvider',\n },\n})\n```\n\n### Additional context\n\n\n\n\n\n\n\n\n\n### Logs\n\n```shell-script\n\n```",[2051,2052],{"name":2028,"color":2029},{"name":2005,"color":2006},2857,"[v3][UAvatar] `UAvatar` breaks when using `@nuxt/image` with custom provider","2025-01-11T15:14:06Z","https://github.com/nuxt/ui/issues/2857",0.75348794,{"description":2059,"labels":2060,"number":2064,"owner":1991,"repository":1992,"state":2033,"title":2065,"updated_at":2066,"url":2067,"score":2068},"### Description\n\nThere is currently no easy way to know what state the modal is in. Adding a `toggle` method would make life very much easier.\n\nI'm willing to make a PR\n\n### Additional context\n\n_No response_",[2061,2062,2063],{"name":1985,"color":1986},{"name":2005,"color":2006},{"name":1988,"color":1989},3720,"feat: add toogle for useOverlay","2025-04-09T15:26:14Z","https://github.com/nuxt/ui/issues/3720",0.76586676,{"description":2070,"labels":2071,"number":2074,"owner":1991,"repository":1992,"state":2033,"title":2075,"updated_at":2076,"url":2077,"score":2078},"### Environment\n\n- Operating System: `Linux`\n- Node Version: `v20.16.0`\n- Nuxt Version: `3.16.1`\n- CLI Version: `3.23.1`\n- Nitro Version: `2.11.7`\n- Package Manager: `pnpm@10.6.3`\n- Builder: `-`\n- User Config: `modules`, `devtools`, `css`, `vite`, `colorMode`, `nitro`, `future`, `compatibilityDate`, `hub`, `app`, `schemaOrg`, `i18n`\n- Runtime Modules: `@nuxthub/core@0.8.18`, `@nuxt/ui@3.0.0`, `@nuxtjs/i18n@9.3.2`, `@nuxtjs/seo@3.0.1`, `nuxt-auth-utils@0.5.17`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.16.1\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/dry-sun-8ddkqr\n\n### Description\n\nThe events of the `USelectMenu` do not work as intended. As you can see in the reproduction, the `change` event of the `UForm` is expected to be emitted every time you select/deselect/create an item, but instead it's emitted only a few seemingly random times.\n\nSwitching to the `input` event on the form has the same random behavior.\n\nI am also surprised programmatically changing the list of values doesn't trigger the `update` event on the `USelectMenu`, but that could be by design and is not really the blocking issue here.\n\nMy reproduction code is a simplification of my real code. It is very similar to the documentation example for creating items, main difference is the multi selection. However the issue also occurs without multi selection.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2072,2073],{"name":2028,"color":2029},{"name":2005,"color":2006},3660,"`USelectMenu` doesn't emit `UForm`.`change` as expected","2025-04-04T16:14:05Z","https://github.com/nuxt/ui/issues/3660",0.7659036,{"description":2080,"labels":2081,"number":2084,"owner":1991,"repository":1992,"state":2033,"title":2085,"updated_at":2086,"url":2087,"score":2088},"### Environment\n\n- Nuxt UI Version: v3.0.0-alpha.7\n- Browser: Chrome | Opera Gx\n- Operating System: Android 12\n\n### Version\n\nv3.0.0-alpha.7\n\n### Reproduction\n\nAfter Adding `overflow-x: auto` Preview\n\n\n\n\n### Description\n\nIn the [NavigationMenu](https://ui3.nuxt.dev/components/navigation-menu) component of Nuxt UI v3.0.0-alpha.7, the horizontal orientation is not displaying correctly due to lack of horizontal overflow handling. When there are multiple items in the menu, items overflow outside the viewport instead of creating a scrollable area. Adding `overflow-x: auto` styling could resolve this issue and improve usability.\n\n### Additional context\n\nWithout `overflow-x: auto` in [NavigationMenu](https://ui3.nuxt.dev/components/navigation-menu)\n\n\n\n\n\n### Logs\n\n_No response_",[2082,2083],{"name":2028,"color":2029},{"name":2005,"color":2006},2468,"Navigation Menu Overflow Bug in Nuxt UI v3.0.0-alpha.7","2025-03-20T00:49:15Z","https://github.com/nuxt/ui/issues/2468",0.76653624,{"description":2090,"labels":2091,"number":2094,"owner":1991,"repository":1992,"state":2033,"title":2095,"updated_at":2096,"url":2097,"score":2098},"### Environment\n\n Operating System: Linux\n- Node Version: v20.15.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.7.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxtjs/i18n@9.1.1, @nuxt/ui@3.0.0-alpha.10, @pinia/nuxt@0.9.0, nuxt-viewport@2.2.0, @nuxthub/core@0.8.7, nuxt-auth-utils@0.5.6, @nuxt/fonts@0.10.3\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.10\n\n### Reproduction\n\n```vue\n//dont work\n\u003CUSelect variant=\"none\" class=\"w-full\" label-key=\"name\" value-key=\"id\" multiple\n @update:model-value=\"testFunctionArray\" @change=\"testFunctionArray\"\n v-model=\"row.original.permissionsModel\" :items=\"permissions\">\n\u003C/USelect>\n```\n\n```vue\n//work fine\n\u003CUSelect variant=\"none\" class=\"w-full\" label-key=\"name\" value-key=\"id\"\n @update:model-value=\"testFunction\" @change=\"testFunction\"\n v-model=\"row.original.permissionModel\" :items=\"permissions\">\n\u003C/USelect>\n```\n\n### Description\n\n`testFunctionArray` is never called if multiple prop is set to true\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2092,2093],{"name":2028,"color":2029},{"name":2005,"color":2006},2953,"USelect with multiple prop does not trigger event when model-value change","2025-01-25T13:12:19Z","https://github.com/nuxt/ui/issues/2953",0.77825475,["Reactive",2100],{},["Set"],["ShallowReactive",2103],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"aCEwhQ28uGx07V9Ee0VfqtiJKJsX_alz3LnxhWZ6kAs":-1},"/nuxt/ui/3126"]