\n\n \u003Ctemplate #panel>\n \u003CRegioloketPreview \n :data=\"row\"\n />\n \u003C/template>\n \u003C/UPopover>\n \u003C/template>\n\n```\n\n",[2887,2890],{"name":2888,"color":2889},"question","d876e3",{"name":2891,"color":2892},"stale","ededed",2435,"@hover event for UTable rows","2025-02-14T01:58:49Z","https://github.com/nuxt/ui/issues/2435",0.7762031,{"description":2899,"labels":2900,"number":2908,"owner":2877,"repository":2878,"state":2879,"title":2909,"updated_at":2910,"url":2911,"score":2912},"### 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```",[2901,2904,2905],{"name":2902,"color":2903},"bug","d73a4a",{"name":2871,"color":2872},{"name":2906,"color":2907},"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.78749883,{"description":2914,"labels":2915,"number":2922,"owner":2877,"repository":2923,"state":2924,"title":2925,"updated_at":2926,"url":2927,"score":2928},"_Improve the design of the modules page with [Raycast](https://www.raycast.com/store) page as the main source of inspiration._\n\n### Todos\n- [ ] Create a responsive design for the modules listing page sync with the API.\n- [ ] Card are external links.\n",[2916,2919],{"name":2917,"color":2918},"design","00bd6f",{"name":2920,"color":2921},"dev","018415",1337,"nuxt.com","closed","Modules Page","2023-10-10T14:44:51Z","https://github.com/nuxt/nuxt.com/issues/1337",0.7412419,{"description":2930,"labels":2931,"number":2935,"owner":2877,"repository":2878,"state":2924,"title":2936,"updated_at":2937,"url":2938,"score":2939},"### Description\n\nHello. Recently I encountered some weird tooltip positioning problems. I use quite a few of tooltips on various places, sometimes nested in accordions. I had a problem to this day, that I managed to solve by setting the UTooltips `popper.strategy` to `absolute` instead of default `fixed`. When using stragegy `fixed`, the tooltip did not render at the correct place, but several (hundred) pixels away, as shown at first screenshot. The correct position of the tooltip should be just below the H3 button, that I was hovering on. \r\n\r\n\r\nAdding insult to injury, it got even worse when I scrolled down.\r\n\r\n\r\nI was just wondering, what caused this issue? Could it be that the component in question was rendered inside an accordion? I did not get this issue when rendering the same component outside of accordion, so I suppose its that. The last thing I want to ask is whether the `absolute` strategy brings some limitations? I checked throughout the application, but I didn't find any problematic places.\r\n\r\nThanks for any answers and awesome work you guys are putting into this project.",[2932,2933],{"name":2888,"color":2889},{"name":2934,"color":2907},"wontfix-v2",1737,"Tooltip positioning problems","2025-03-28T17:58:46Z","https://github.com/nuxt/ui/issues/1737",0.75355023,{"description":2941,"labels":2942,"number":2954,"owner":2877,"repository":2877,"state":2924,"title":2955,"updated_at":2956,"url":2957,"score":2958},"### Describe the feature\n\nHi,\r\n\r\n### Current Problem\r\nNuxt js currently preload then execute the scripts at the bottom of the body for priority boosting. But `link:rel=preload` doesn't have greater browser support so I'm browser which doesn't support it will take long time to fetch and execute it.\r\n\r\n\r\n\r\n### Solution\r\n\r\nI propose an alternate approach to load first party script with defer, where `\u003Cscript defer>` will be added to the , with the objective of streamlining the overall loading sequence, modeling web-performance best practices, and moving away from preload as a crutch for signal boosting.\r\n\r\nBrowser compatibility (MDN) -:\r\n\r\n`\u003Clink rel=\"preload\" />`\r\n\r\n\r\n`\u003Cscript defer>`\r\n\r\n\r\n### Advantages \r\n\r\n- Scripts wont block the HTML parsing as intended.\r\n\r\n\r\n- Improvements in FCP, LCP metric, faster time to visual-completeness.\r\n\r\n- Additional optimization and predictability given the guaranteed order of execution of defer scripts.\r\n\r\n\r\n### Issue when implementing\r\n\r\nThis works perfectly fine for `type=module`(automatically adds defer attr) scripts too but for them preloading having some benefits so we need to conditionally add preload tag if it is targeted to new module based syntax.\r\n\r\n### References\r\n\r\nCurrent Next js implementation (Please check this out for better understanding)-: https://github.com/vercel/next.js/discussions/24938\r\n\r\nAbout scripts loading-: https://gist.github.com/jakub-g/385ee6b41085303a53ad92c7c8afd7a6\r\n\r\nIssues of preloading-: https://docs.google.com/document/d/1ZEi-XXhpajrnq8oqs5SiW-CXR3jMc20jWIzN5QRy1QA/\r\n___\r\n\n\n### Additional information\n\n- [X] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://v3.nuxtjs.org/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/framework/discussions) and [issues](https://github.com/nuxt/framework/issues).",[2943,2945,2948,2951],{"name":2868,"color":2944},"8DEF37",{"name":2946,"color":2947},"discussion","538de2",{"name":2949,"color":2950},"3.x","29bc7f",{"name":2952,"color":2953},"performance","E84B77",15072,"Improve loading sequence of hydration `\u003Cscript />` 🚀 ","2023-11-20T11:10:34Z","https://github.com/nuxt/nuxt/issues/15072",0.76136494,{"description":2960,"labels":2961,"number":2964,"owner":2877,"repository":2878,"state":2924,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v22.11.0\n- Nuxt Version: 3.15.0\n- CLI Version: 3.17.2\n- Nitro Version: 2.10.4\n- Package Manager: bun@1.1.37\n- Builder: -\n- User Config: default\n- Runtime Modules: nuxt-mapbox@1.6.1, @nuxt/image@1.8.1, @nuxt/ui@3.0.0-alpha.10, @nuxtjs/supabase@1.4.5, @vueuse/nuxt@10.11.1, @nuxtjs/i18n@8.5.6, @vueuse/motion/nuxt@2.2.6\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.0-alpha.10\n\n### Reproduction\n\n\u003CUTable\n :data=\"data\"\n :columns=\"columnsTable\"\n @select=\"select\"\n/>\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```",[2962,2963],{"name":2902,"color":2903},{"name":2871,"color":2872},3010,"UTable row click event UI3","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/3010",0.770942,{"description":2970,"labels":2971,"number":2977,"owner":2877,"repository":2923,"state":2924,"title":2978,"updated_at":2979,"url":2980,"score":2981},"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",[2972,2974],{"name":2902,"color":2973},"ff281a",{"name":2975,"color":2976},"a11y","2CD658",1060,"css:has on firefox","2023-06-06T12:14:32Z","https://github.com/nuxt/nuxt.com/issues/1060",0.77148664,{"description":2983,"labels":2984,"number":2990,"owner":2877,"repository":2923,"state":2924,"title":2991,"updated_at":2992,"url":2993,"score":2994},"",[2985,2987],{"name":2868,"color":2986},"1ad6ff",{"name":2988,"color":2989},"responsive","1cd1c6",821,"[Navbar] Add color mode switch in mobile aside nav","2023-02-15T12:31:01Z","https://github.com/nuxt/nuxt.com/issues/821",0.7738642,{"description":2996,"labels":2997,"number":2999,"owner":2877,"repository":2878,"state":2924,"title":3000,"updated_at":3001,"url":3002,"score":3003},"### 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! :)",[2998],{"name":2902,"color":2903},1722,"Nuxt UI - UInput Type Number - weird behaviour with decimals","2025-03-28T17:59:29Z","https://github.com/nuxt/ui/issues/1722",0.77499086,["Reactive",3005],{},["Set"],["ShallowReactive",3008],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fmR1tbo4oi0EVs0oDb2T2MTLwjAColOzWcrg5u2NwdTA":-1},"/nuxt/nuxt.com/1353"]