\n\n \u003Ctemplate #panel>\n \u003CRegioloketPreview \n :data=\"row\"\n />\n \u003C/template>\n \u003C/UPopover>\n \u003C/template>\n\n```\n\n",[2867,2870],{"name":2868,"color":2869},"question","d876e3",{"name":2871,"color":2872},"stale","ededed",2435,"nuxt","ui","open","@hover event for UTable rows","2025-02-14T01:58:49Z","https://github.com/nuxt/ui/issues/2435",0.7830852,{"description":2882,"labels":2883,"number":2893,"owner":2874,"repository":2875,"state":2876,"title":2894,"updated_at":2895,"url":2896,"score":2897},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.13.1\n- Nuxt Version: 3.16.2\n- CLI Version: 3.24.1\n- Nitro Version: 2.11.8\n- Package Manager: pnpm@10.8.1\n- Builder: -\n- User Config: app, compatibilityDate, css, devtools, devServer, eslint, imports, modules, runtimeConfig, sourcemap, ssr, icon, ui, colorMode\n- Runtime Modules: @nuxt/eslint@1.3.0, @nuxt/ui@3.0.2, @vueuse/nuxt@13.0.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/condescending-mcnulty-k5jgtf\n\n### Description\n\nHi 👋,\n\nI’ve noticed an issue with the `ColorPicker` component related to color precision.\n\n🐛 Bug Description\n\nWhen I manually input the hex value `#123456` into the `ColorPicker`, it gets changed to `#123354` immediately.\n\nAfter digging into the source code, I found that the component uses `colortranslator` and internally converts colors via HSL using HSLObject. It appears that during the RGB → HSL → RGB round-trip, there’s a slight loss of precision, which results in the hex value being altered.\n\nIt seems that the issue might be caused by the `decimals` option being set to `2`, while the default value in `colortranslator` is `6`. \n\nhttps://github.com/nuxt/ui/blob/2b315fd855666b02d32373769c8617dd713a8d0a/src/runtime/components/ColorPicker.vue#L104-L109\n\nOr `Math.round` here:\n\nhttps://github.com/nuxt/ui/blob/2b315fd855666b02d32373769c8617dd713a8d0a/src/runtime/components/ColorPicker.vue#L28-L36\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2884,2887,2890],{"name":2885,"color":2886},"bug","d73a4a",{"name":2888,"color":2889},"v3","49DCB8",{"name":2891,"color":2892},"triage","ffffff",3948,"[ColorPicker] ColorPicker alters manually entered hex value due to precision loss in colortranslator","2025-04-22T09:04:57Z","https://github.com/nuxt/ui/issues/3948",0.79811245,{"description":2899,"labels":2900,"number":2902,"owner":2874,"repository":2875,"state":2903,"title":2904,"updated_at":2905,"url":2906,"score":2907},"### 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! :)",[2901],{"name":2885,"color":2886},1722,"closed","Nuxt UI - UInput Type Number - weird behaviour with decimals","2025-03-28T17:59:29Z","https://github.com/nuxt/ui/issues/1722",0.7407577,{"description":2909,"labels":2910,"number":2915,"owner":2874,"repository":2875,"state":2903,"title":2916,"updated_at":2917,"url":2918,"score":2919},"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",[2911,2914],{"name":2912,"color":2913},"feature","A27AF6",{"name":2888,"color":2889},2129,"Vue compatibility","2024-11-21T09:41:35Z","https://github.com/nuxt/ui/issues/2129",0.7484914,{"description":2921,"labels":2922,"number":2923,"owner":2874,"repository":2924,"state":2903,"title":2925,"updated_at":2926,"url":2927,"score":2928},"### 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,"nuxt.com","[Document] nuxt modules page has been crashed.","2023-10-10T14:44:55Z","https://github.com/nuxt/nuxt.com/issues/1353",0.7684658,{"description":2930,"labels":2931,"number":2935,"owner":2874,"repository":2874,"state":2903,"title":2936,"updated_at":2937,"url":2938,"score":2939},"Patak recently [posted about improving the PR template of the vite repo](https://elk.zone/m.webtoo.ls/@patak/112155977618264831 ) and merged the improvements in https://github.com/vitejs/vite/pull/16266.\r\n\r\nI agree with these two points in his PR description:\r\n\r\n> - I don't think the \"purpose of this pull request\" section is useful. ... we already have this information in the PR title as we use conventional commit (fix, feat, docs, chore, etc).\r\n> - Nobody is completing the \"Before submitting the PR\" section. The checkboxes doesn't render so it isn't good UX for contributors.\r\n\r\nWhat do you think about changing this in the Nuxt repo as well?",[2932],{"name":2933,"color":2934},"chore","D0F1A9",26561,"PR template improvement","2024-03-29T19:26:33Z","https://github.com/nuxt/nuxt/issues/26561",0.77813214,{"description":2941,"labels":2942,"number":2949,"owner":2874,"repository":2874,"state":2903,"title":2950,"updated_at":2951,"url":2952,"score":2953},"## Motivation\r\n\r\nVue is a very international community with a lot of presence in non-english regions like China.\r\n\r\n- Many community members have proposed their help here https://github.com/nuxt/nuxt/discussions/16054\r\n- China have a (non-official ?) Chinese version of the Nuxt docs https://github.com/nuxt/nuxt/discussions/16208 : https://nuxt.com.cn/\\\r\n- A Russian translation has been discussed https://github.com/nuxt/nuxt/discussions/17351\r\n- A Ukrainian translation have been discussed https://github.com/nuxt/nuxt/issues/19926\r\n\r\nFormkit recently released an AI translation for their website docs https://formkit.com/ in 4 languages. \r\n\r\nWe could take a similar approach and combine it with the existing community translations.\r\nIn my opinion, an AI approach needs to be compatible with existing contributions, and manual modifications.\r\n\r\n## Implementation idea\r\n\r\n*Disclaimer: I'm sharing some of my thoughts about how we could build such a system, to gauge community interest in doing so. Suggestion and feedback would be very appreciated!*\r\n\r\nWe would use i18n for the docs website to handle the language strings (related docus issue https://github.com/nuxt-themes/docus/issues/770)\r\nThen to keep the translations in sync with the english source, we could run logic (maybe within the CI), that is triggered when english docs gets merged in nuxt/nuxt, and automatically open PRs for each language with a LLM translation inserted at the right location. \r\nWith such a system, the Nuxt community/team can review the LLM output and modify it before merging it for their language. \r\nAll new additions to the docs must be done in English, so that they are reflected anywhere.\r\nIf translations PRs are an issue for maintainers, we could move all of this to another repo `nuxt-international` or something.\r\n\r\nMany of the Nuxt/Unjs team members already speak 2 or more languages, so we could start out with these languages.\r\nIf this system is successful, it can be expanded and applied to other things, such as the UnJS ecosystem, or integrated with docus\r\n\r\n### Create entire translations from scratch\r\n\r\nWhile working from human written translation is more accurate, we could also experiment with entirely AI written translations. We could build a tool that translates all markdown docs content from the english source into a new language.\r\n\r\n## Bonus\r\n\r\nLook at worldwide trends for Nuxt over the last year : https://trends.google.com/trends/explore?q=nuxt,nuxtjs,nuxt.js&hl=en-GB\r\n\r\nInterestingly enough, there's more search interest for Nuxt in China than in english speaking countries.\r\n\r\n\u003Cimg width=\"1204\" alt=\"image\" src=\"https://github.com/nuxt/nuxt/assets/13395944/98146ec6-c6d7-479d-afb9-bcb7ee13bf4f\">\r\n\r\nIn fact, the anglosphere rank significantly lower than other areas.\r\n\r\n\r\n### Additional information\r\n\r\n- [X] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2943,2946],{"name":2944,"color":2945},"documentation","5319e7",{"name":2947,"color":2948},"discussion","538de2",21926,"[Proposal] Documentation Translation Strategy","2024-12-12T19:49:15Z","https://github.com/nuxt/nuxt/issues/21926",0.7826575,{"description":2955,"labels":2956,"number":2959,"owner":2874,"repository":2875,"state":2903,"title":2960,"updated_at":2961,"url":2962,"score":2963},"### Environment\n\n- Operating System: Linux\n- Node Version: v20.9.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.1.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @vueuse/nuxt@11.3.0, @nuxt/ui@3.0.0-alpha.9, @pinia/nuxt@0.5.5, nuxt-auth-sanctum@0.5.2, nuxt-i18n-micro@1.33.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.9\n\n### Reproduction\n\nhttps://ui3.nuxt.dev/components/input-menu#value-key\n\n### Description\n\nIn components `\u003CUSelectMenu />` and `\u003CUInputMenu />` filter is not working when using an array of object and the \"value-key\" prop\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2957,2958],{"name":2885,"color":2886},{"name":2888,"color":2889},2730,"USelectMenu | UInputMenu filter not working with value-key","2024-12-05T13:48:55Z","https://github.com/nuxt/ui/issues/2730",0.7857616,{"labels":2965,"number":2966,"owner":2874,"repository":2874,"state":2903,"title":2967,"updated_at":2968,"url":2969,"score":2970},[],12943,"Is there a plan for the internationalization of docs?","2023-01-19T16:39:56Z","https://github.com/nuxt/nuxt/issues/12943",0.7864851,{"labels":2972,"number":2973,"owner":2874,"repository":2874,"state":2903,"title":2967,"updated_at":2974,"url":2975,"score":2970},[],13014,"2023-01-19T16:42:38Z","https://github.com/nuxt/nuxt/issues/13014",["Reactive",2977],{},["Set"],["ShallowReactive",2980],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f0Hjk4IcnhGzjOPjk_jR9uTr5EadXebN0AFVEOL1armA":-1},"/nuxt/nuxt.com/821"]