\n\n\n### Description\n\nIn Nuxt UI v3, the \u003CUTable /> component does not provide any trigger event when clicking on a table row. In contrast, the v2 version included the @select event, which allowed developers to handle row clicks effectively. This regression impacts the ability to implement common interaction patterns, such as handling row selection or performing actions based on user clicks.\n\nDoes Nuxt UI v3 have an event similar to the @select event from v2 for the \u003CUTable /> component? Specifically, is there a way to trigger an event when a table row is clicked?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2017,2020],{"name":2018,"color":2019},"bug","d73a4a",{"name":1988,"color":1989},3010,"UTable row click event UI3","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/3010",0.7506378,{"description":2027,"labels":2028,"number":2035,"owner":1991,"repository":1991,"state":2009,"title":2036,"updated_at":2037,"url":2038,"score":2039},"Over the years, Nuxt's Discord server has become the best place to get help, thanks to a vibrant community of users and moderators. But as the Nuxt user base increases, the \"Help\" channels start to show some limitations. We think that [Github Discussions](https://docs.github.com/en/discussions) would be more useful and manageable for the community.\r\n\r\n## Discord limitations\r\n\r\n- As there are lots of questions, if no answer is provided in a few hours, the lonely question gets flooded by the new ones. This is of course frustrating for the user asking for help.\r\n- At the same time, answering all of the questions is very time consuming.\r\n- The value provided by the answers is time-limited, as they can't be archived, searched, and referenced later, and are not indexed by search engines.\r\n\r\n## Github Discussions\r\n\r\nAfter consulting the Nuxt framework team and key contributors and moderators, we came to the conclusion that Github Discussions seem to check all requirements :\r\n\r\n- Public\r\n- Search, Categorize, Upvote answers\r\n- A Ranking system for active contributors which shows more recognition for the most helpful community members.\r\n\r\nA [Q&A channel](https://github.com/nuxt/nuxt.js/discussions/categories/q-a) has already been created, and we want to increase its usage in the coming weeks.\r\n\r\n## What's coming next ?\r\n\r\nDiscord channels won't be closed, as we feel they are still useful for broad topics (Should I use X, How do you see the future of pattern Y...) and one-liners, but every help request and specific questions would find a better place in a Github Discussion.\r\n\r\nAn introduction to Github discussions, contribution guidelines and Code of Conduct will be edited and pinned [here](https://github.com/nuxt/nuxt.js/discussions) to guide everyone in the transition.\r\n\r\nWe're confident this transition will increase the quality of support. Feel free to ask any questions or give us feedback below! 👇\r\n",[2029,2032],{"name":2030,"color":2031},"enhancement","8DEF37",{"name":2033,"color":2034},"2.x","d4c5f9",9248,"☝️ Moving support from Discord to Github Discussions","2023-01-22T15:52:51Z","https://github.com/nuxt/nuxt/issues/9248",0.75265074,{"description":2041,"labels":2042,"number":2044,"owner":1991,"repository":1992,"state":2009,"title":2045,"updated_at":2046,"url":2047,"score":2048},"### Description\r\n\r\nHey!\r\nIm using an UInput type number and encountered something strange.\r\nIt is not possible to write the number \"1.04\" or \"0.06\". The culprit seems to be the \"0\" after the \".\".\r\nFurther example of working decimal: \"1.14\", 1.56\"\r\nIt works fine if you use \",\" as a comma but my mobile phones number keyboard only provides \".\".\r\n\r\nThe same behvaiour can be tested here:\r\nhttps://ui.nuxt.com/components/input\r\n\r\nIm using Mac and Chrome to test.\r\n\r\nLet me know what you think! :)",[2043],{"name":2018,"color":2019},1722,"Nuxt UI - UInput Type Number - weird behaviour with decimals","2025-03-28T17:59:29Z","https://github.com/nuxt/ui/issues/1722",0.7544992,{"description":2050,"labels":2051,"number":2057,"owner":1991,"repository":2008,"state":2009,"title":2058,"updated_at":2059,"url":2060,"score":2061},"has() css selector isn't enabled by default on Firefox.\nthe next major release version of Firefox will enable it by default but due to poor performance on old architecture, Firefox disable the selector by default. It is possible to enable it by setting layout.css.has-selector.enabled to true in about:config",[2052,2054],{"name":2018,"color":2053},"ff281a",{"name":2055,"color":2056},"a11y","2CD658",1060,"css:has on firefox","2023-06-06T12:14:32Z","https://github.com/nuxt/nuxt.com/issues/1060",0.76272416,{"description":2063,"labels":2064,"number":2066,"owner":1991,"repository":2008,"state":2009,"title":2067,"updated_at":2068,"url":2069,"score":2070},"\n",[2065],{"name":2018,"color":2053},702,"[Project] Error on `ProjectHeader` on project without files","2023-02-15T12:32:46Z","https://github.com/nuxt/nuxt.com/issues/702",0.7727964,{"description":2072,"labels":2073,"number":2075,"owner":1991,"repository":1992,"state":2009,"title":2076,"updated_at":2077,"url":2078,"score":2079},"### Description\n\nEmpty value for UInput with type number sets an empty string to the model. This results in a type error instead of a required error for validation. It makes me, and probably the end users, confused. Can this be somehow resolved?\r\n\r\n\u003Cimg width=\"366\" alt=\"image\" src=\"https://github.com/user-attachments/assets/0d9cf5a3-c439-49c8-9de6-e3c34dbdeb8c\">\r\n",[2074],{"name":1985,"color":1986},2090,"empty value for UInput with type number ","2025-03-28T17:30:59Z","https://github.com/nuxt/ui/issues/2090",0.7774317,{"description":2081,"labels":2082,"number":2083,"owner":1991,"repository":2008,"state":2009,"title":2084,"updated_at":2085,"url":2086,"score":2087},"### Environment\n\nbrowser chrome\n\n### Reproduction\n\nopen https://nuxt.com/modules in browser.\n\n### Describe the bug\n\n\u003Cimg width=\"1271\" alt=\"image\" src=\"https://github.com/nuxt/nuxt/assets/32301380/7363e730-5eda-4fee-8790-375987e293ef\">\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[],1353,"[Document] nuxt modules page has been crashed.","2023-10-10T14:44:55Z","https://github.com/nuxt/nuxt.com/issues/1353",0.7791595,{"description":2089,"labels":2090,"number":2095,"owner":1991,"repository":1992,"state":2009,"title":2096,"updated_at":2097,"url":2098,"score":2099},"After many requests from the community (nuxt/ui#187, nuxt/ui#298, nuxt/ui#543, nuxt/ui#850, nuxt/ui#1514, etc.), the goal would be to make `@nuxt/ui` compatible for non-Nuxt apps as a Vite plugin I guess.\r\n\r\nThe minimal features would be to:\r\n\r\n- Run Tailwind CSS vite plugin\r\n- Inject components\r\n- Inject composables\r\n- Use `@iconify/vue` instead of `@nuxt/icon` (we don't need that much complexity I guess)\r\n- Use VueUse https://vueuse.org/core/useDark/#usedark instead of `@nuxtjs/color-mode`\r\n- Make Nuxt specific imports (`#imports`, `#build`, etc.) work\r\n- Make Nuxt specific composables (`useAppConfig`, ~~`useId`~~, etc.) work\r\n- Make theming with `app.config.ts` work in some way",[2091,2094],{"name":2092,"color":2093},"feature","A27AF6",{"name":1988,"color":1989},2129,"Vue compatibility","2024-11-21T09:41:35Z","https://github.com/nuxt/ui/issues/2129",0.78250146,["Reactive",2101],{},["Set"],["ShallowReactive",2104],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"JRuB7oBNUnKqbNpo0eyyHFFN5fGM4mh4VJB2gPceGOU":-1},"/nuxt/ui/2435"]