\n \u003C/UCarousel>\n\u003C/template>\n\n### Description\n\nSimulate the behavior of https://m3.material.io/components/carousel/overview, Carousel will repeatedly calculate is-snapped in an infinite loop\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2885,2886,2887],{"name":2866,"color":2867},{"name":2869,"color":2870},{"name":2872,"color":2873},3883,"[Carousel] Unable to differentiate item sizes","2025-04-14T08:19:21Z","https://github.com/nuxt/ui/issues/3883",0.74611014,{"description":2894,"labels":2895,"number":2896,"owner":2875,"repository":2897,"state":2877,"title":2898,"updated_at":2899,"url":2900,"score":2901},"ssr : false, network unavailable environment.\nDue to security, we need to deploy it to an internal server.\n\nIf you use the icon after installation without any special options, the icon cannot be displayed when you check it on the server after deployment.\n\nMaybe it's because communication with the iconify server is impossible, right?\n\nWhat can I do in this case?\n\nThank :)",[],363,"icon","in a closed network Can't I use the icon?","2025-02-27T04:31:17Z","https://github.com/nuxt/icon/issues/363",0.77296287,{"description":2903,"labels":2904,"number":2908,"owner":2875,"repository":2876,"state":2909,"title":2910,"updated_at":2911,"url":2912,"score":2913},"I am trying to create breadcrumbs that dynamically reflect route parameters in Nuxt, specifically for routes with dynamic segments. For example, when editing a user at the route `/users/:userId/edit`, the breadcrumbs should look like this: `Users > :userId > Edit`.\n\nI understand that I can use overrides with `useBreadcrumbItems()` to manually define the breadcrumb structure, but the challenge arises when different routes require different overrides. Since `useBreadcrumbItems()` can only be used at the top level of the `setup` function, I am unable to recreate or modify the breadcrumb items based on route changes. This results in errors when trying to update the breadcrumbs dynamically as the route changes.\n\nIs there a recommended way to handle this scenario where breadcrumbs need to be updated dynamically based on route parameters?",[2905],{"name":2906,"color":2907},"question","d876e3",2305,"closed","Unable to Dynamically Generate Dynamic Breadcrumbs","2024-10-04T07:52:07Z","https://github.com/nuxt/ui/issues/2305",0.74723595,{"description":2915,"labels":2916,"number":2919,"owner":2875,"repository":2876,"state":2909,"title":2920,"updated_at":2921,"url":2922,"score":2923},"### Description\n\nMight have missed this in the beta 2 docs, but curious how we're supposed to close the current `Modal` or `Slideover` instance from within the component using the new `useOverlay` composable. I see a few references to `useOverlayInstance` in other issue but that composable doesn't seem to be available in the current beta.\n\nThanks!",[2917,2918],{"name":2906,"color":2907},{"name":2869,"color":2870},3429,"How to get current modal/slideover instance?","2025-03-02T17:44:50Z","https://github.com/nuxt/ui/issues/3429",0.7474016,{"description":2925,"labels":2926,"number":2928,"owner":2875,"repository":2876,"state":2909,"title":2929,"updated_at":2930,"url":2931,"score":2932},"### Description\r\n\r\nHi, is there any way to disable the error template? \r\n\r\nI just tried to set an empty template, but this creates a div with some classes that create a slight jump because of the set class mt-2... and overwriting from the template is also not possible...\r\n\r\nI need to do this because I need to show some custom logic where error messages are used as hints.\r\n\r\ncheers,\r\ngregor",[2927],{"name":2906,"color":2907},2100,"disabling formgroup error template","2024-09-03T08:41:36Z","https://github.com/nuxt/ui/issues/2100",0.7503104,{"description":2934,"labels":2935,"number":2941,"owner":2875,"repository":2875,"state":2909,"title":2942,"updated_at":2943,"url":2944,"score":2945},"### Version\r\n```>= 1.0-rc0```\r\n\r\n### Reproduction links\r\nhttps://glitch.com/edit/#!/nuxt-rc0\r\nhttps://nuxt-rc0.glitch.me/\r\nhttps://nuxt-rc0.glitch.me/about\r\n\r\n### Steps to reproduce\r\nLoad the page above, and start typing into the search field. The input element is set to trigger an update of the query string on keypress.\r\n\r\n### What is expected?\r\nYou should be able to continue typing after the first character, and the query string url should continue updating with what you type. \r\n\r\n### What is actually happening?\r\nAfter every keypress, the form field loses focus and you have to click inside again to be able to type the next character.\r\n\r\nAdditionally, if the typing is done on the about page in the above demo, then it also scrolls to the top of the page after each keypress, despite the custom scroll Behaviour disabling that.\r\n\r\n### Extra Information\r\nI noticed this change in behavior when I upgraded from 1.0.0-alpha.4 to 1.0.0-rc3, but after checking the previous versions it seems to have started in 1.0.0-rc0.\r\n\r\nLinks to a glitch to see a working previous version\r\nhttps://glitch.com/edit/#!/nuxt-alpha4\r\nhttps://nuxt-alpha4.glitch.me/\r\nhttps://nuxt-alpha4.glitch.me/about\r\n\r\nTo rule out changes upstream in vue router causing this, I created a jsfiddle using version 2.7.0 of vue-router (same as nuxt 1.0.0-rc3 uses). The behaviour *does not* exist in that test:\r\nhttps://jsfiddle.net/benosman/octu95ra/\r\n\r\nNote: This issue has been rewritten, hopefully to make it clearer to understand what the problem is.\r\n\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1112\">#c1112\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2936,2938],{"name":2906,"color":2937},"cc317c",{"name":2939,"color":2940},"2.x","d4c5f9",1255,"Pages are fully re-rendered when just query string changes - focus on active element lost","2023-01-18T15:41:00Z","https://github.com/nuxt/nuxt/issues/1255",0.7532177,{"description":2947,"labels":2948,"number":2951,"owner":2875,"repository":2876,"state":2909,"title":2952,"updated_at":2953,"url":2954,"score":2955},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v20.10.0`\n- Nuxt Version: `3.14.159`\n- CLI Version: `3.15.0`\n- Nitro Version: `2.10.4`\n- Package Manager: `npm@10.9.0`\n- Builder: `-`\n- User Config: `default`\n- Runtime Modules: `@nuxt/ui@3.0.0-alpha.8`, `nuxt-svgo@4.0.9`\n- Build Modules: `-`\n\n### Version\n\nv3.0.0-alpha.8\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-h9x1yj\n\n### Description\n\nWhen using the vertical NavigationMenu, `defaultOpen` doesn't work...\n\n\"When orientation is vertical, a [Collapsible](https://ui3.nuxt.dev/components/collapsible) component is used to display children. You can control the open state of each item using the `open` and `defaultOpen` properties.\" - [link here](https://ui3.nuxt.dev/components/navigation-menu#orientation).\n\nPS I tried `open` as well: same issue.\n\n### Additional context\n\n```vue\n\u003Cscript setup lang=\"ts\">\n/* Types */\nimport type { NavigationMenuItem } from '#ui/types';\n\nconst items = ref\u003CNavigationMenuItem[][]>([\n [\n {\n label: 'Menu 1',\n defaultOpen: true, // ! This doesn't work\n open: true, // ! This doesn't work\n children: [\n {\n label: 'Submenu 1',\n to: '/submenu-1',\n },\n {\n label: 'Submenu 2',\n to: '/submenu-2',\n },\n ],\n },\n {\n label: 'Menu 2',\n defaultOpen: true, // ! This doesn't work\n open: true, // ! This doesn't work\n children: [\n {\n label: 'Submenu 1',\n to: '/submenu-1',\n },\n {\n label: 'Submenu 2',\n to: '/submenu-2',\n },\n ],\n },\n ],\n]);\n\u003C/script>\n\n\u003Ctemplate>\n \u003Cdiv class=\"h-full\">\n \u003CUNavigationMenu orientation=\"vertical\" :items=\"items\" />\n \u003C/div>\n\u003C/template>\n```\n\n### Logs\n\n```shell-script\n\n```",[2949,2950],{"name":2866,"color":2867},{"name":2869,"color":2870},2755,"Veritcal NavigationMenu - `defaultOpen` doesn't work","2024-11-26T10:29:27Z","https://github.com/nuxt/ui/issues/2755",0.7569736,{"description":2957,"labels":2958,"number":2960,"owner":2875,"repository":2876,"state":2909,"title":2961,"updated_at":2962,"url":2963,"score":2964},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v20.14.0\r\n- Nuxt Version: 3.12.4\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: pnpm@9.7.1\r\n- Builder: -\r\n- User Config: runtimeConfig, extends, modules, ui, colorMode, routeRules, devtools, typescript, future, eslint, nitro, i18n, compatibilityDate\r\n- Runtime Modules: @nuxt/eslint@0.5.0, @nuxt/fonts@0.7.1, @nuxt/ui@2.18.4, @vueuse/nuxt@10.11.0, @nuxtjs/i18n@8.5.0\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Version\r\n\r\nPro 1.4.1\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-ui-u6tm1b?file=app.vue\r\n\r\n### Description\r\n\r\nWhen using a `v-model` prop with some initial object values (such as fetched already selected data from backend), the `\u003CUSelectMenu>` component doesn't show these as selected and seems to ignore them completely.\r\n\r\nEven when selecting the same objects again, it just seems to add them to the array and disregard anything, that was there previously.\r\n\r\n### Additional context\r\n\r\nThe behaviour changes when setting the `by` prop. In my case, I set it to `id`, after which I can see the object as selected, **but only** in the dropdown.\r\nThis also allows me to edit the data as normal. (Select/Deselect)\r\nHowever the button itself still shows `0 selected`.\r\n\r\n### Logs\r\n\r\n_No response_",[2959],{"name":2866,"color":2867},2086,"SelectMenu ignoring initial object values","2024-11-12T17:12:26Z","https://github.com/nuxt/ui/issues/2086",0.75775284,{"description":2966,"labels":2967,"number":2974,"owner":2875,"repository":2876,"state":2909,"title":2975,"updated_at":2976,"url":2977,"score":2978},"### For what version of Nuxt UI are you suggesting this?\n\nv2.x\n\n### Description\n\nWhen validating an object, a FormGroup does not display validations of specific properties (at least not with details).\n\nWould it make sense for the name `myobj` to display errors from anything that looks like `myobj\\..*` ? it could show all of them, each on a newline.\n\n### Additional context\n\nhttps://github.com/nuxt/ui/issues/1898",[2968,2971,2973],{"name":2969,"color":2970},"enhancement","a2eeef",{"name":2972,"color":2873},"wontfix-v2",{"name":2869,"color":2870},2569,"Display zod validation errors based on prefix","2024-11-11T18:28:09Z","https://github.com/nuxt/ui/issues/2569",0.7656068,["Reactive",2980],{},["Set"],["ShallowReactive",2983],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fuB01HeOijNDqFr5DmjKkFTRdWAJD_u2oXNG-VBIyO8o":-1},"/nuxt/ui/3963"]