\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```",[3020,3023,3026],{"name":3021,"color":3022},"bug","d73a4a",{"name":3024,"color":3025},"v3","49DCB8",{"name":3027,"color":3028},"triage","ffffff",3883,"nuxt","ui","open","[Carousel] Unable to differentiate item sizes","2025-04-14T08:19:21Z","https://github.com/nuxt/ui/issues/3883",0.73723567,{"description":3038,"labels":3039,"number":3043,"owner":3030,"repository":3031,"state":3032,"title":3044,"updated_at":3045,"url":3046,"score":3047},"### Environment\n\nsandbox\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/admiring-herschel-qyt4kh\n\n### Description\n\n`app.config`\n\n```\nbutton: {\n compoundVariants: [\n {\n color: 'primary',\n variant: 'soft',\n class: {\n base: 'text-green-500',\n leadingIcon: 'text-red-500'\n }\n },\n ]\n}\n```\n\nif button defined like without `active` the icon is red, but text is green\n```\n\u003CUButton\n label=\"Label\"\n color=\"primary\"\n variant=\"soft\"\n icon=\"mdi-account\"\n />\n```\n\nsame result is expected when using `active`, but `leadingIcon` is ignored\n```\n\u003CUButton\n label=\"Label\"\n active\n active-color=\"primary\"\n active-variant=\"soft\"\n icon=\"mdi-account\"\n @click.prevent=\"active = !active\"\n/>\n```\n\n### Additional context\n\n\u003Cimg width=\"202\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/0756fb1c-772c-44ae-855d-90aba304bd9e\" />",[3040,3041,3042],{"name":3021,"color":3022},{"name":3024,"color":3025},{"name":3027,"color":3028},3972,"Different result than static for active-color & active-variant","2025-04-24T15:30:39Z","https://github.com/nuxt/ui/issues/3972",0.75337934,{"description":3049,"labels":3050,"number":3056,"owner":3030,"repository":3057,"state":3032,"title":3058,"updated_at":3059,"url":3060,"score":3061},"https://github.com/nuxt/ui/commit/f7604e565f717001a4d4c2974cf23559a3f01c21",[3051,3053],{"name":3021,"color":3052},"ff281a",{"name":3054,"color":3055},"upstream","78BDDB",1830,"nuxt.com","typecheck error because of `@nuxt/ui` Drawer component","2025-03-23T14:59:06Z","https://github.com/nuxt/nuxt.com/issues/1830",0.7599551,{"description":3063,"labels":3064,"number":3065,"owner":3030,"repository":3057,"state":3032,"title":3066,"updated_at":3067,"url":3068,"score":3069},"the current a11y score on nuxt.com is `83` (from lighthouse), pretty sure we can max it out\n\n- [x] I can work on this if no one's gonna take it?",[],1837,"fix: improve a11y","2025-03-26T16:24:17Z","https://github.com/nuxt/nuxt.com/issues/1837",0.7689476,{"description":3071,"labels":3072,"number":3076,"owner":3030,"repository":3031,"state":3032,"title":3077,"updated_at":3078,"url":3079,"score":3080},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.1.0`\n- Nuxt Version: `3.16.2`\n- CLI Version: `3.24.0`\n- Nitro Version: `2.11.8`\n- Package Manager: `yarn@4.7.0`\n- Builder: `-`\n- User Config: `modules`, `ssr`, `components`, `app`, `css`, `runtimeConfig`, `compatibilityDate`, `nitro`, `vite`, `eslint`\n- Runtime Modules: `@pinia/nuxt@0.10.1`, `pinia-plugin-persistedstate/nuxt@4.2.0`, `@nuxt/ui@3.0.2`, `dayjs-nuxt@2.1.11`, `@nuxt/eslint@1.3.0`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/sandbox/festive-feather-mzq49q\n\nIn the second select (which is wrapped in a form tag), don't select anything, and click save to submit the form.\n\nIt should show the browser \"this input is required\" tooltip.\n\n### Description\n\nI can't really understand why/how this happens. Sometimes, the `required` prop on a Select component will not prevent the form to be submitted. But sometimes it's working fine.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3073,3074,3075],{"name":3021,"color":3022},{"name":3024,"color":3025},{"name":3027,"color":3028},3882,"Select required sometimes not working","2025-04-14T08:11:48Z","https://github.com/nuxt/ui/issues/3882",0.7696938,{"description":3082,"labels":3083,"number":3089,"owner":3030,"repository":3031,"state":3032,"title":3090,"updated_at":3091,"url":3092,"score":3093},"### Description\n\nRelated: #2907 \n\nFor many form controls, such as buttons, inputs, checkboxes, radio buttons, text areas, and more, there is no need to have stylistic handling of disabled states by default as they mostly will never reach it.\n\nIf we take for example the most common type of online forms, the registration/login form, there is typically an email input and a password input, none of which will ever be disabled. Having the disabled styling on them simply results in more clutter in the HTML and larger payloads, thus reducing performance. \n\nAnd this doesn't even touch on other use cases of form controls that can never be disabled as per the spec, like using `UButton`'s builtin navigation support when making aesthetic links to other content.\n\nA big performance improvement can be made in this aspect by introducing a new `disabled` variant for form controls that will be false by default. Only if explicitly set on will it add all styling related to the disabled state.\n\n### Additional context\n\n_No response_",[3084,3087,3088],{"name":3085,"color":3086},"enhancement","a2eeef",{"name":3024,"color":3025},{"name":3027,"color":3028},3092,"`disabled` variant in form controls","2025-01-14T09:54:50Z","https://github.com/nuxt/ui/issues/3092",0.7818371,{"description":3095,"labels":3096,"number":3097,"owner":3030,"repository":3057,"state":3098,"title":3099,"updated_at":3100,"url":3101,"score":3102},"### Environment\n\nNot necessary\n\n### Reproduction\n\nhttps://nuxt.com/\n\n### Describe the bug\n\n1. Go to https://nuxt.com/\r\n2. Check the alt tags for images in cards after `A solution to cover all your needs`. Possibly many others too.\r\n3. See that the value is `[object Object] image`.\r\n\r\n\u003Cimg width=\"1204\" alt=\"image\" src=\"https://user-images.githubusercontent.com/640208/203802739-c306c698-53dc-47d6-878c-324ec09dc08f.png\">\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[],1231,"closed","docs: alt tag of images is faulty","2023-04-12T10:10:59Z","https://github.com/nuxt/nuxt.com/issues/1231",0.7435374,{"description":3104,"labels":3105,"number":3109,"owner":3030,"repository":3031,"state":3098,"title":3110,"updated_at":3111,"url":3112,"score":3113},"### 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",[3106],{"name":3107,"color":3108},"question","d876e3",2100,"disabling formgroup error template","2024-09-03T08:41:36Z","https://github.com/nuxt/ui/issues/2100",0.74364626,{"description":3115,"labels":3116,"number":3119,"owner":3030,"repository":3031,"state":3098,"title":3120,"updated_at":3121,"url":3122,"score":3123},"### 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!",[3117,3118],{"name":3107,"color":3108},{"name":3024,"color":3025},3429,"How to get current modal/slideover instance?","2025-03-02T17:44:50Z","https://github.com/nuxt/ui/issues/3429",0.7459283,{"description":3125,"labels":3126,"number":3128,"owner":3030,"repository":3031,"state":3098,"title":3129,"updated_at":3130,"url":3131,"score":3132},"### Environment\r\n\r\n- Operating system: \"android 14\"\r\n- Nuxt Version: \"3.13.2\"\r\n- Vue Version: \"3.5.8\"\r\n- \r\n\r\n### Version\r\n\r\nv2.18.6\r\n\r\n### Reproduction\r\n\r\nhttps://ui.nuxt.com/components/dropdown\r\n\r\n\r\n\r\n\r\n\r\n### Description\r\n\r\nclicking on the dropdown button doesn't work in mobile view. the \"click\" event & the \"touchstart\" event, call the same function (toggle dropdown visibility), and neutralize each other. (basically, click event opens the dropdown, the touchstart event, closes the dropdown)\r\n\r\nI tested it and in both android 14 & in windows, firefox (mobile view mode), I got the same result.\r\n\r\n### Additional context\r\n\r\n\r\n\r\n\r\n### Logs\r\n\r\n_No response_",[3127],{"name":3021,"color":3022},2261,"\"UDropdown\": Toggle NOT Working in Mobile. click event & touchstart event neutralize each other.","2024-10-01T13:00:59Z","https://github.com/nuxt/ui/issues/2261",0.75148726,["Reactive",3134],{},["Set"],["ShallowReactive",3137],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fpew_85CfNQKdWSB08EHC60KwFJ2P0cl9TVhOcOrZ2io":-1},"/nuxt/ui/2385"]