\n \u003C/UTooltip>\n \u003C/template>\n\u003C/UNavigationMenu>\n```",[3087,3088,3089],{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3026,"color":3027},4050,"NavigationMenu has no way to apply a tooltip.","2025-05-10T11:36:41Z","https://github.com/nuxt/ui/issues/4050",0.70770276,{"description":3096,"labels":3097,"number":3100,"owner":3029,"repository":3030,"state":3053,"title":3101,"updated_at":3102,"url":3103,"score":3104},"### Description\n\nI'm wondering how I can style the active dot on the component level through the :ui prop.",[3098,3099],{"name":3062,"color":3063},{"name":3023,"color":3024},4228,"Carousel: Can I style the active dot through the :ui prop?","2025-05-26T15:48:31Z","https://github.com/nuxt/ui/issues/4228",0.7138452,{"description":3106,"labels":3107,"number":3111,"owner":3029,"repository":3030,"state":3053,"title":3112,"updated_at":3113,"url":3114,"score":3115},"### Description\n\nWhen a dot is selected in the UCarousel component, we get no attribute in the element : \n\n- no data-selected\n- no aria-current for accessibility\n\nSince there is no dots/dot slot, we have no possibility to style these dots when selected or not. The only difference is the bg style being either bg-accented or bg-inverted, which is overwritten if we actually style the background.\n\nIs there any way to add these attributes ? At least for accessibility.\n\n### Additional context\n\n_No response_",[3108,3109,3110],{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3026,"color":3027},4403,"UCarousel selected dot has no attribute","2025-07-07T10:09:58Z","https://github.com/nuxt/ui/issues/4403",0.7157747,{"description":3117,"labels":3118,"number":3129,"owner":3029,"repository":3030,"state":3053,"title":3130,"updated_at":3131,"url":3132,"score":3133},"### Environment\n\n- Nuxt Vesrion: '3.15.1'\n- Nuxt/ui Version: '3.0.1'\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.15.1\n\n### Reproduction\n\nhttps://github.com/nuxt/ui/pull/2251\n\n### Description\n\nThis issue was previously addressed and fixed in [PR #2251](https://github.com/nuxt/ui/pull/2251). However, after upgrading to Nuxt UI v3.0.1, the dir prop no longer exists, making it impossible to switch the direction of the Carousel.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3119,3122,3125,3126],{"name":3120,"color":3121},"bug","d73a4a",{"name":3123,"color":3124},"needs reproduction","CB47CF",{"name":3023,"color":3024},{"name":3127,"color":3128},"closed-by-bot","ededed",3705,"Missing \"dir\" Prop in Carousel Component After Nuxt UI v3.0.1 Update","2025-05-31T02:09:01Z","https://github.com/nuxt/ui/issues/3705",0.73100907,{"description":3135,"labels":3136,"number":3139,"owner":3029,"repository":3030,"state":3053,"title":3140,"updated_at":3141,"url":3142,"score":3143},"### Description\n\nI saw that some components (like `Modal` or `Slideover`) have the \"trigger\" fully replaceable, meanwhile others like `Select` and `SelectMenu` cannot be fully replaced. Because of that, introducing another slot to replace the entire trigger would be nice imho. But I would define it as the default slot, not a named one (like `trigger` or something else) to remain consistent with the modal/slideover one.\nThe problem is that it would introduce a breaking change, so I don't know what is the way you want to proceed.\nWhat do you think about this?\nMentioning @sandros94 as I talked about this with him on Discord.\n\n### Additional context\n\nTo have a look on this, I did some changes in a branch in my fork: \u003Chttps://github.com/nuxt/ui/compare/v3...zAlweNy26:nuxt-ui:feat/select-trigger>",[3137,3138],{"name":3020,"color":3021},{"name":3023,"color":3024},4009,"Standardize trigger slot in components","2025-05-10T17:57:56Z","https://github.com/nuxt/ui/issues/4009",0.7396197,["Reactive",3145],{},["Set"],["ShallowReactive",3148],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fseZn9YJt2C5NmYXlsAcxn21Nab7GJ4QYBDWcUxHDfAc":-1},"/nuxt/ui/4494"]