\n```\nbut it is not optimal as typescript is complaining about the types.\n\nI would suggest something like\n```vue\n\u003CUTable :data idKey=\"id\" :paginationOptions=\"{ manualPagination: true, rowCount: data?.totalItems }\" />\n```\n\nwhere `idKey` is a `keyof T` or it can be the entire `getRowId` method imported from TanStack.\n\nI can open a PR about this if it's fine :)\n\n### Additional context\n\n_No response_",[2937,2940],{"name":2938,"color":2939},"enhancement","a2eeef",{"name":2907,"color":2908},3255,"Unique row ID for `UTable` component","2025-02-15T17:44:03Z","https://github.com/nuxt/ui/issues/3255",0.7290232,{"description":2947,"labels":2948,"number":2952,"owner":2910,"repository":2911,"state":2912,"title":2953,"updated_at":2954,"url":2955,"score":2956},"### Environment\n\nDocs page: https://ui3.nuxt.dev/components/input\n\nSorry if this repo isn't the right place to report bugs about the docs. The \"edit this page\" link on the docs lead me to this repository. \n\nThis could be a minor thing but it's still not ideal.\n\nClicking a link on the right hand side prompts firefox if it should save the password \n\n\n\nPerhaps to mitigate this, the input field has to differ from the docs code and not use type password\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nhttps://ui3.nuxt.dev as of 28.01.2025\n\n### Reproduction\n\n1. Go to https://ui3.nuxt.dev/components/input\n2. Click a link on the right hand side\n3. Browser should ask if it should save the password\n\n### Description\n\nDocs page prompts browser to save the password due to a `\u003Cinput type=\"password\">` in an example\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2949,2950,2951],{"name":2921,"color":2922},{"name":2924,"color":2925},{"name":2907,"color":2908},3195,"Docs page for Input causes browser to prompt if it should save the password from a password example input","2025-01-29T10:08:23Z","https://github.com/nuxt/ui/issues/3195",0.73343354,{"description":2958,"labels":2959,"number":2966,"owner":2910,"repository":2911,"state":2912,"title":2967,"updated_at":2968,"url":2969,"score":2970},"### Description\n\nI would like to propose adding native Infinity Scrolling support to the USelectMenu component and much more for efficiently handling and displaying large datasets.\n\nCurrently, I have implemented a workaround by using a combination of a MutationObserver and dynamic class binding to detect when the dropdown menu is rendered. Once the menu is detected, I attach an onScroll event listener to implement custom infinity scrolling. Below is an example of how this has been achieved:\n\n```\n\u003Ctemplate>\n \u003CUSelectMenu :ui-menu=\"{ strategy: 'merge', base: `scroller-${randomHash}` }\" />\n\u003C/template>\n```\n\n```\n\u003Cscript setup lang=\"ts\">\nconst randomHash = Math.random().toString(36).substring(7);\n\nonMounted(() => {\n const observer = new MutationObserver((mutationsList) => {\n for (const mutation of mutationsList) {\n if (mutation.type === \"childList\") {\n const element = document.querySelector(`.scroller-${randomHash}`);\n if (element) {\n // Element has been found, add an onScroll event listener\n observer.disconnect();\n break;\n }\n }\n }\n });\n\n observer.observe(document.body, {\n childList: true,\n subtree: true, \n });\n\n onBeforeUnmount(() => {\n observer.disconnect();\n });\n});\n\u003Cscript/>\n```\n\n### Additional context\n\n_No response_",[2960,2961,2964],{"name":2938,"color":2939},{"name":2962,"color":2963},"wontfix-v2","ffffff",{"name":2965,"color":2963},"triage",3072,"Add Infinity Scrolling Support to USelectMenu and much more components for Handling Large Datasets","2025-04-02T15:17:48Z","https://github.com/nuxt/ui/issues/3072",0.73389703,{"description":2972,"labels":2973,"number":2977,"owner":2910,"repository":2911,"state":2912,"title":2978,"updated_at":2979,"url":2980,"score":2981},"### Description\n\nIs there a way to prevent popovers from closing when clicking outside the popover?",[2974,2975,2976],{"name":2904,"color":2905},{"name":2962,"color":2963},{"name":2907,"color":2908},2245,"Popover close-prevented","2024-11-10T09:20:02Z","https://github.com/nuxt/ui/issues/2245",0.7347767,{"description":2983,"labels":2984,"number":2990,"owner":2910,"repository":2911,"state":2912,"title":2991,"updated_at":2992,"url":2993,"score":2994},"### Description\n\nI really love all the work that went into this, but it's currently connected to vue-router for `Link` and `Pagination` components. I would love to see these become optional dependencies so it can be used with projects that do not use `vue-router`.\n\nMaybe there is some way to stub out the link components to enable support for Inertia \\ default HTML?",[2985,2986,2987],{"name":2904,"color":2905},{"name":2907,"color":2908},{"name":2988,"color":2989},"vue","42b883",3001,"How likely is it that we'll see a routerless version?","2025-04-14T08:47:28Z","https://github.com/nuxt/ui/issues/3001",0.73894006,{"description":2996,"labels":2997,"number":3002,"owner":2910,"repository":3003,"state":2912,"title":3004,"updated_at":3005,"url":3006,"score":3007},"Hello,\r\n\r\nNuxt baseURL is ignored in production.\r\n\r\nGiven `app.baseURL: '/myapp/'`:\r\n\r\nActual behavior: fonts are dumped in `.output/public/_fonts/` but resolved as `https://domain.com/_fonts/`\r\n\r\nExpected behavior: fonts should indeed be dumped in `.output/public/_fonts/` but font urls should point to `https://domain.com/myapp/_fonts/`\r\n\r\nIt works fine in development when path assets.prefix is set to `/myapp/_fonts`. However if this path is set to production, fonts are dumped in `.output/public/myapp/_fonts/` and resolved to `https://domain.com/myapp/_fonts/` which doesn't exist as it's now `https://domain.com/myapp/myapp/_fonts/`.\r\n\r\nNuxt fonts: 0.5.1\r\nNuxt: 3.11.1\r\n\r\nMinimal reproduction: https://stackblitz.com/edit/github-4bvlvu?file=nuxt.config.ts (then manually navigate to /myapp in the preview)\r\n",[2998,2999],{"name":2921,"color":2922},{"name":3000,"color":3001},"upstream","4E99F0",96,"fonts","Nuxt baseURL ignored when resolving cached font path","2024-09-04T02:54:14Z","https://github.com/nuxt/fonts/issues/96",0.7400907,{"description":3009,"labels":3010,"number":3013,"owner":2910,"repository":3014,"state":2912,"title":3015,"updated_at":3016,"url":3017,"score":3018},"",[3011],{"name":2938,"color":3012},"1ad6ff",208,"nuxt.com","Put content file history in media too","2023-02-15T12:31:55Z","https://github.com/nuxt/nuxt.com/issues/208",0.7425971,{"description":3020,"labels":3021,"number":3026,"owner":2910,"repository":2911,"state":2912,"title":3027,"updated_at":3028,"url":3029,"score":3030},"### Description\n\nIf i try to define the position of the notification using the `ui` prop `\u003CUNotifications :ui=\"{position: 'top-0 right-0'}\" />`\r\nthe \"default\" configuration is applied as well (`bottom-0 end-0 `) this happens also if defining the position using the app.config.ts.. I'm assuming i'm doing it wrong.. please advice.. \r\n",[3022,3025],{"name":3023,"color":3024},"duplicate","cfd3d7",{"name":2904,"color":2905},2180,"Notification position","2024-09-11T14:08:24Z","https://github.com/nuxt/ui/issues/2180",0.74445826,["Reactive",3032],{},["Set"],["ShallowReactive",3035],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$feP17e0aP81Ve3Gwp_ntoQBndTOgWBN226qO6iVgSGQQ":-1},"/nuxt/ui/3710"]