\n \u003C/UTooltip>\n \u003C/template>\n\u003C/UNavigationMenu>\n```",[2935,2936,2937],{"name":2883,"color":2884},{"name":2869,"color":2870},{"name":2887,"color":2888},4050,"NavigationMenu has no way to apply a tooltip.","2025-05-10T11:36:41Z","https://github.com/nuxt/ui/issues/4050",0.79420996,{"description":2944,"labels":2945,"number":2948,"owner":2872,"repository":2873,"state":2914,"title":2949,"updated_at":2950,"url":2951,"score":2952},"### Description\n\nThe concepts of Chips and Badges are reversed. \n\nChip is the component with text, to represent status or options selected, that can also have counters, icons aside labels and in some cases a remove button.\nBadge is the component that have a notification or a counter\n\nIn my opinion:\n\nThis is a chip ⤵️\n\n\nAnd this is a Badge ⤵️\n\n\nAn example\nhttps://medium.com/design-bootcamp/ux-blueprint-03-badges-vs-chips-tags-a-friendly-guide-e38ab2217be3#:~:text=Key%20Differences,users%20navigate%20and%20manage%20content.",[2946,2947],{"name":2866,"color":2867},{"name":2869,"color":2870},3282,"The concepts of Chips and Badges are reversed","2025-02-10T09:38:39Z","https://github.com/nuxt/ui/issues/3282",0.7945406,{"description":2954,"labels":2955,"number":2958,"owner":2872,"repository":2873,"state":2914,"title":2959,"updated_at":2960,"url":2961,"score":2962},"### Description\n\nI can see there was some changes [here](https://github.com/nuxt/ui/pull/3123) which is great.\n\nI'm just wondering why the 'help' property was excluded from these additions?\n\nThank you!",[2956,2957],{"name":2866,"color":2867},{"name":2869,"color":2870},3685,"Was UFormField 'help' property excluded from the aria-describedby update for any specific reason?","2025-03-26T12:47:39Z","https://github.com/nuxt/ui/issues/3685",0.7946575,{"description":2964,"labels":2965,"number":2968,"owner":2872,"repository":2873,"state":2914,"title":2969,"updated_at":2970,"url":2971,"score":2972},"### 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>",[2966,2967],{"name":2883,"color":2884},{"name":2869,"color":2870},4009,"Standardize trigger slot in components","2025-05-10T17:57:56Z","https://github.com/nuxt/ui/issues/4009",0.80180115,{"description":2974,"labels":2975,"number":2976,"owner":2872,"repository":2977,"state":2914,"title":2978,"updated_at":2979,"url":2980,"score":2981},"https://www.figma.com/file/OLlmzoVQ7FSBh4FJJORNpl/nuxt.com?node-id=4452%3A42741",[],472,"nuxt.com","[Company] Careers integration `/company/careers`","2023-02-15T12:31:28Z","https://github.com/nuxt/nuxt.com/issues/472",0.8021879,["Reactive",2983],{},["Set"],["ShallowReactive",2986],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f7sxY8i85dGM6eTmDj_RBlAIkCy0qE3H9ZN56GNmBQhw":-1},"/nuxt/ui/4165"]