\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```",[1998,2001,2004],{"name":1999,"color":2000},"bug","d73a4a",{"name":2002,"color":2003},"v3","49DCB8",{"name":2005,"color":2006},"triage","ffffff",3883,"ui","[Carousel] Unable to differentiate item sizes","2025-04-14T08:19:21Z","https://github.com/nuxt/ui/issues/3883",0.77810043,{"description":2014,"labels":2015,"number":2020,"owner":1988,"repository":2008,"state":1990,"title":2021,"updated_at":2022,"url":2023,"score":2024},"I currently have the problem that we have to integrate our SPA into a larger application. And with that, we also inherit the CSS of the outer application. And that's where it gets really ugly: they have partially written classes in their own CSS files that use the TW naming scheme (m, p, gap, shadow, etc.), and then add `!important` to these declarations. \n\nOne of the big problems with Nuxt UI is that there is no prefixing of Tailwind classes. So we started writing TW utilities with a prefix for the affected classes. This is then transferred to app.config. The second problem was the merge process that app.config uses. Usually the names have to match. If I want to have a `p-4` from the config (because px values with !important were entered in the outer CSS), I created the class `p-00`, which replaces the `p-4` class and thus clears the way for the prefixed TW class `o-p-4`.\n\nSo far so good, but I can't use it with popovers like SelectMenu. No matter what I do, the class `shadow-lg` remains. The other devs of the main application have entered a rather ugly shadow with important there. \n\nIs there another prop like 'content' that I can use to replace `shadow-lg`? I'm not a fan of `!important`, but at this point I can only work this way.\n\nFurthermore, it would be really nice if you could really overwrite the sections in app.config instead of just merging them (apart from prefixing the TW classes). There are certain stylings that you won't use, but then they are in the element",[2016,2019],{"name":2017,"color":2018},"question","d876e3",{"name":2002,"color":2003},3874,"Changing Shadow Classes on Popover and SelectMenu","2025-04-13T13:53:28Z","https://github.com/nuxt/ui/issues/3874",0.78936076,{"description":2026,"labels":2027,"number":2028,"owner":1988,"repository":2029,"state":1990,"title":2030,"updated_at":2031,"url":2032,"score":2033},"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,"nuxt.com","fix: improve a11y","2025-03-26T16:24:17Z","https://github.com/nuxt/nuxt.com/issues/1837",0.791202,{"description":2035,"labels":2036,"number":2039,"owner":1988,"repository":2008,"state":2040,"title":2041,"updated_at":2042,"url":2043,"score":2044},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.x\n\n### Description\n\nI would like to have some way to customize the modal width. There isn't not even a \"size\" property and I can't change it by the \"ui\" prop.\n\n### Additional context\n\n_No response_",[2037,2038],{"name":2017,"color":2018},{"name":2002,"color":2003},2774,"closed","[v3][UModal] Size property or way to customize modal width","2024-11-26T14:41:52Z","https://github.com/nuxt/ui/issues/2774",0.71097344,{"description":2046,"labels":2047,"number":2049,"owner":1988,"repository":2008,"state":2040,"title":2050,"updated_at":2051,"url":2052,"score":2053},"### 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_",[2048],{"name":1999,"color":2000},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.74455667,{"description":2055,"labels":2056,"number":2057,"owner":1988,"repository":2029,"state":2040,"title":2058,"updated_at":2059,"url":2060,"score":2061},"### 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,"docs: alt tag of images is faulty","2023-04-12T10:10:59Z","https://github.com/nuxt/nuxt.com/issues/1231",0.76746726,{"description":2063,"labels":2064,"number":2067,"owner":1988,"repository":2029,"state":2040,"title":2068,"updated_at":2069,"url":2070,"score":2071},"https://volta.s3.fr-par.scw.cloud/Clean_Shot_2022_11_16_at_17_20_41_8b14c455c0.mp4\n",[2065],{"name":1999,"color":2066},"ff281a",981,"[docs]/guide/directory-structure/app.config: missing content + broken nav ","2022-12-07T06:14:48Z","https://github.com/nuxt/nuxt.com/issues/981",0.7733306,{"description":2073,"labels":2074,"number":2075,"owner":1988,"repository":2029,"state":2040,"title":2076,"updated_at":2077,"url":2078,"score":2079},"Hover effect icon https://www.notion.so/nuxt/Hover-effect-icon-6bd48c2f9b23479689993c1492c287de",[],1087,"[Review] HomeCardItem","2023-02-15T12:31:07Z","https://github.com/nuxt/nuxt.com/issues/1087",0.7746825,{"description":2081,"labels":2082,"number":2085,"owner":1988,"repository":2008,"state":2040,"title":2086,"updated_at":2087,"url":2088,"score":2089},"### Description\n\nI've recently upgraded to NuxtUi [v3.0.2](https://github.com/nuxt/ui/releases/tag/v3.0.2) from [v3.0.0-beta.2](https://github.com/nuxt/ui/releases/tag/v3.0.0-beta.2) and I'm having an issue with the search term prop on the component.\n\nWhen using the input with search and multiselect, I'd like the search term to clear as the user selects menu items. I was able to achieve this, in previous versions, by using a v-model on the search term and calling a function to clear the search term on the `update:ModelValue` event. Unfortunately, this isn't working on the most recent version.\n\nIt appears that `update:ModelValue` is being emitted and I am able to clear the searchTerm ref value. However, the change doesn't propagate to the component unless I hit the tab key or click out and click back into the component.\n\nIs there a potential workaround or could this become a feature request to include a prop which clears the search term on item select?",[2083,2084],{"name":2017,"color":2018},{"name":2002,"color":2003},3782,"InputMenu Clear Search Term on Select","2025-04-08T10:37:15Z","https://github.com/nuxt/ui/issues/3782",0.7800482,["Reactive",2091],{},["Set"],["ShallowReactive",2094],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"yv0liaDDBnkouqfYrLQaKIUHPBIjSlfGKi7Ke2y4G90":-1},"/nuxt/ui/3843"]