is used","2025-04-10T06:07:28Z","https://github.com/nuxt/icon/issues/356",0.75651556,{"description":2876,"labels":2877,"number":2867,"owner":2868,"repository":2881,"state":2870,"title":2882,"updated_at":2883,"url":2884,"score":2874},"I suppose this is related to how we selected the first element",[2878],{"name":2879,"color":2880},"bug","ff281a","nuxt.com","On command palettes, arrow down must be pressed twice to go to next result","2023-02-15T12:32:13Z","https://github.com/nuxt/nuxt.com/issues/356",{"description":2886,"labels":2887,"number":2867,"owner":2868,"repository":2890,"state":2870,"title":2891,"updated_at":2892,"url":2893,"score":2874},"### 🐛 The bug\n\nIn the reproduction project added two pages. In page1 adsense script is used. Accessing this page triggers \"error loading dynamically imported module: https://nuxtstarterpkwfkx-l1p5--3000--1b4252dd.local-corp.webcontainer.io/_nuxt/pages/page1.vue\" after some time.\n\n### 🛠️ To reproduce\n\nhttps://stackblitz.com/edit/nuxt-starter-kzs9wacl?file=pages%2Fpage1.vue\n\n### 🌈 Expected behavior\n\nadsense iframe to load\n\n### ℹ️ Additional context\n\n_No response_",[2888],{"name":2879,"color":2889},"d73a4a","scripts","error loading dynamically imported module, when using adsense script","2025-02-12T08:39:18Z","https://github.com/nuxt/scripts/issues/356",{"description":2895,"labels":2896,"number":2903,"owner":2868,"repository":2868,"state":2870,"title":2904,"updated_at":2905,"url":2906,"score":2907},"### Version\r\n```>= 1.0-rc0```\r\n\r\n### Reproduction links\r\nhttps://glitch.com/edit/#!/nuxt-rc0\r\nhttps://nuxt-rc0.glitch.me/\r\nhttps://nuxt-rc0.glitch.me/about\r\n\r\n### Steps to reproduce\r\nLoad the page above, and start typing into the search field. The input element is set to trigger an update of the query string on keypress.\r\n\r\n### What is expected?\r\nYou should be able to continue typing after the first character, and the query string url should continue updating with what you type. \r\n\r\n### What is actually happening?\r\nAfter every keypress, the form field loses focus and you have to click inside again to be able to type the next character.\r\n\r\nAdditionally, if the typing is done on the about page in the above demo, then it also scrolls to the top of the page after each keypress, despite the custom scroll Behaviour disabling that.\r\n\r\n### Extra Information\r\nI noticed this change in behavior when I upgraded from 1.0.0-alpha.4 to 1.0.0-rc3, but after checking the previous versions it seems to have started in 1.0.0-rc0.\r\n\r\nLinks to a glitch to see a working previous version\r\nhttps://glitch.com/edit/#!/nuxt-alpha4\r\nhttps://nuxt-alpha4.glitch.me/\r\nhttps://nuxt-alpha4.glitch.me/about\r\n\r\nTo rule out changes upstream in vue router causing this, I created a jsfiddle using version 2.7.0 of vue-router (same as nuxt 1.0.0-rc3 uses). The behaviour *does not* exist in that test:\r\nhttps://jsfiddle.net/benosman/octu95ra/\r\n\r\nNote: This issue has been rewritten, hopefully to make it clearer to understand what the problem is.\r\n\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1112\">#c1112\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2897,2900],{"name":2898,"color":2899},"question","cc317c",{"name":2901,"color":2902},"2.x","d4c5f9",1255,"Pages are fully re-rendered when just query string changes - focus on active element lost","2023-01-18T15:41:00Z","https://github.com/nuxt/nuxt/issues/1255",0.77707195,{"description":2909,"labels":2910,"number":2916,"owner":2868,"repository":2917,"state":2870,"title":2918,"updated_at":2919,"url":2920,"score":2921},"### Environment\n\n------------------------------\n- Operating System: Windows_NT\n- Node Version: v20.15.0\n- Nuxt Version: 3.13.2\n- CLI Version: 3.14.0\n- Nitro Version: 2.9.7\n- Package Manager: pnpm@9.10.0\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Version\n\nv3.0.0-alpha.5\n\n### Reproduction\n\n No need. It'd be great if we had a stackblitz or codepen etc. playground example repo for v3 so that everyone can get a repo up quickly. It'd increase feedback.\n\n### Description\n\nWith v2 button text was automatically centered but now it is not? Is this expected because of radix-ui transition?\n\n```\n \u003CUButton type=\"submit\" block size=\"xl\">\n {{ $t(\"auth.login.action\") }}\n \u003C/UButton>\n```\n\n\n\n```\n \u003CUButton\n :label=\"$t('auth.login.actionKinder')\"\n type=\"submit\"\n block\n class=\"text-center\"\n size=\"xl\"\n />\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2911,2913],{"name":2898,"color":2912},"d876e3",{"name":2914,"color":2915},"v3","49DCB8",2317,"ui","Button 'block' attribute doesn't center it's content","2024-10-07T13:08:58Z","https://github.com/nuxt/ui/issues/2317",0.77721775,{"description":2923,"labels":2924,"number":2930,"owner":2868,"repository":2917,"state":2870,"title":2931,"updated_at":2932,"url":2933,"score":2934},"### Environment\n\n- **Operating System**: Windows 11\n- **Browsers**: Firefox, Chrome (latest for each)\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.x (docs)\n\n### Reproduction\n\nOn **Windows 11**, hitting `windows key + k`, per the docs for `meta_k` when using `defineShortcuts`, which is what looks like the search command palette on the docs is using, does not get passed into the website itself (or even the browser). I've tried ctrl and other keybinds with no success either. \n\nI've tested on both Chrome and Firefox, neither work.\n\n### Description\n\nUsing the following javascript in the browser console on each:\n```\nwindow.addEventListener(\"keydown\", function (event) {\n console.log(event)\n})\n\nwindow.addEventListener(\"keyup\", function (event) {\n console.log(event)\n})\n```\n\nA few things I notice:\n1. Holding Windows key (`meta`) does trigger the keydown event, but pressing `k`, Windows intercepts, and doesn't trigger a keydown event. Assume this is because Windows 10 or 11 is intercepting for this \"cast\" feature (below).\n2. Pressing `k` first, then Windows key (`meta`), both trigger keydown, but neither trigger keyup. `k` triggers keydown, but then Windows key (`meta`) doesn't.\n\n\n\n### Additional context\n\ntl;dr: probably easiest to support `ctrl+k`. `ctrl+f` is typical for basic browser text search, so `ctrl+k` makes the most sense (and it's what most sites use). I've never seen sites use windows keys for anything, because it's meant for _windows_ functionality. Alternatively, supporting `/` would be nice, some sites use this.\n\nNot critical, just the keybind to search docs faster. Plus, the search icon is so small in the docs navbar that I often misclick when trying to search the docs.\n\n### Logs\n\n```shell-script\n\n```",[2925,2926,2927],{"name":2879,"color":2889},{"name":2914,"color":2915},{"name":2928,"color":2929},"triage","ffffff",3869,"bug(docs): search keybind (for command palette) non-functional on windows","2025-04-28T10:40:08Z","https://github.com/nuxt/ui/issues/3869",0.77762413,{"description":2936,"labels":2937,"number":2941,"owner":2868,"repository":2881,"state":2870,"title":2942,"updated_at":2943,"url":2944,"score":2945},"",[2938],{"name":2939,"color":2940},"enhancement","1ad6ff",408,"Scroll to file in tree on select from command palette","2023-02-15T12:32:16Z","https://github.com/nuxt/nuxt.com/issues/408",0.78109646,{"description":2947,"labels":2948,"number":2941,"owner":2868,"repository":2949,"state":2870,"title":2950,"updated_at":2951,"url":2952,"score":2945},"It would be helpful to test if a given plugin is *not* added, for example.\r\n\r\nThis is needed rather than using the jest `.not` helper because this code fails, if a *different* plugin is injected:\r\n```js\r\n test('should not inject optional plugin', () => {\r\n expect(ctx).not.toNuxtPluginAdded({\r\n src: expect.stringContaining('templates/optional-plugin.js'),\r\n })\r\n })\r\n```",[],"test-utils","feat: add corresponding negative jest matchers","2023-12-02T00:13:09Z","https://github.com/nuxt/test-utils/issues/408",{"description":2954,"labels":2955,"number":2957,"owner":2868,"repository":2917,"state":2870,"title":2958,"updated_at":2959,"url":2960,"score":2961},"### Environment\n\nOperating System: Linux\r\nNode Version: v20.15.1\r\nNuxt Version: 3.13.0\r\nCLI Version: 3.13.1\r\nNitro Version: 2.9.7\r\nPackage Manager: bun@1.1.27\r\nBuilder: -\r\nUser Config: devtools, extends, modules, ui\r\nRuntime Modules: @nuxt/ui@2.18.4\r\nBuild Modules: -\n\n### Version\n\nv2.18.4\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-ggpvlu?file=app.vue\n\n### Description\n\nWhen adding `NuxtLink` props (ex: to: '/') to the items of `Dropdown`, causes the next warn:\r\n```\r\nruntime-core.esm-bundler.js?v=13c1e3b9:50 [Vue warn]: Extraneous non-emits event listeners (pointerenter, focus) were passed to component but could not be automatically inherited because component renders fragment or text root nodes. If the listener is intended to be a component custom event listener only, declare it using the \"emits\" option. \r\n at \u003CRouterLink ref=fn to=\"/\" activeClass=undefined ... > \r\n at \u003CNuxtLink key=0 ref_for=true to=\"/\" ... > \r\n at \u003CMenuItems class=\"relative focus:outline-none overflow-y-auto scroll-py-1 divide-y divide-gray-200 dark:divide-gray-700 ring-1 ring-gray-200 dark:ring-gray-700 rounded-md shadow-lg bg-white dark:bg-gray-800\" static=\"\" > \r\n at \u003CBaseTransition appear=true persisted=false mode=undefined ... > \r\n at \u003CTransition appear=\"\" enterActiveClass=\"transition duration-100 ease-out\" enterFromClass=\"transform scale-95 opacity-0\" ... > \r\n at \u003CMenu as=\"div\" class=\"relative inline-flex text-left rtl:text-right\" onMouseleave=fn\u003ConMouseLeave> > \r\n at \u003CDropdown items= (4) [Array(1), Array(2), Array(2), Array(1)] popper= {placement: 'bottom-start'} > \r\n at \u003CApp key=4 > \r\n at \u003CNuxtRoot>\r\nwarn$1 @ runtime-core.esm-bundler.js?v=13c1e3b9:50\r\nrenderComponentRoot @ runtime-core.esm-bundler.js?v=13c1e3b9:6383\r\ncomponentUpdateFn @ runtime-core.esm-bundler.js?v=13c1e3b9:5065\r\nrun @ reactivity.esm-bundler.js?v=13c1e3b9:150\r\ninstance.update @ runtime-core.esm-bundler.js?v=13c1e3b9:5118\r\nupdateComponent @ runtime-core.esm-bundler.js?v=13c1e3b9:4927\r\nprocessComponent @ runtime-core.esm-bundler.js?v=13c1e3b9:4861\r\npatch @ runtime-core.esm-bundler.js?v=13c1e3b9:4366\r\ncomponentUpdateFn @ runtime-core.esm-bundler.js?v=13c1e3b9:5074\r\nrun @ reactivity.esm-bundler.js?v=13c1e3b9:150\r\ninstance.update @ runtime-core.esm-bundler.js?v=13c1e3b9:5118\r\ncallWithErrorHandling @ runtime-core.esm-bundler.js?v=13c1e3b9:200\r\nflushJobs @ runtime-core.esm-bundler.js?v=13c1e3b9:413\r\nPromise.then\r\nqueueFlush @ runtime-core.esm-bundler.js?v=13c1e3b9:323\r\nqueueJob @ runtime-core.esm-bundler.js?v=13c1e3b9:317\r\n(anonymous) @ runtime-core.esm-bundler.js?v=13c1e3b9:5112\r\nresetScheduling @ reactivity.esm-bundler.js?v=13c1e3b9:235\r\ntriggerEffects @ reactivity.esm-bundler.js?v=13c1e3b9:279\r\ntriggerRefValue @ reactivity.esm-bundler.js?v=13c1e3b9:1045\r\nset value @ reactivity.esm-bundler.js?v=13c1e3b9:1092\r\nprefetch @ nuxt-link.js?v=13c1e3b9:203\r\n(anonymous) @ nuxt-link.js?v=13c1e3b9:226\r\n(anonymous) @ nuxt-link.js?v=13c1e3b9:351\r\nShow 23 more frames\r\nShow less\r\n\r\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2956],{"name":2879,"color":2889},2105,"`UDropdown` Extraneous non-emits event listeners (pointerenter, focus)","2024-09-06T10:17:27Z","https://github.com/nuxt/ui/issues/2105",0.78810763,{"description":2963,"labels":2964,"number":2966,"owner":2868,"repository":2917,"state":2870,"title":2967,"updated_at":2968,"url":2969,"score":2970},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v20.11.1\n- Nuxt Version: 3.15.4\n- CLI Version: 3.22.1\n- Nitro Version: 2.10.4\n- Package Manager: yarn@1.22.19\n- Builder: -\n- User Config: devtools, modules, compatibilityDate\n- Runtime Modules: @nuxt/ui@2.20.0\n- Build Modules: -\n\n### Version\n\nv2.20.0 and later\n\n### Reproduction\n\nI could not get Stackblitz to work when changing Nuxt UI versions due to internal 503 errors. Please forgive me for using codesandbox instead.\n\n**Nuxt UI v2.19.1** - Working as expected. You can edit and tab between inputs.\nhttps://codesandbox.io/p/devbox/nuxt-v2-19-1-lz5zvk\n\n**Nuxt UI v2.20.0** - Cursor position lost when typing. Second column (email) uses `.lazy` which allows typing but loses focus when tabbing after edit.\nhttps://codesandbox.io/p/devbox/nuxt-v2-20-0-x9xylj\n\n\n\n\n\n### Description\n\nRelease v2.20.0 includes PR #2600 which redraws every table column slot on _any_ changes to the table source data. This introduces significant performance impact on large tables and makes it difficult for users to interact with inputs within tables since the redraw will lose cursor position. This also makes it impossible to tab between columns when data changes.\n\nI intend to submit a PR which reverts the changes made in #2600.\n\n### Additional context\n\nI demonstrate in https://github.com/nuxt/ui/issues/2004#issuecomment-2671025567 that the issue reported which prompted PR #2006 was a misunderstanding and was not related to table behavior at all. Therefore, that PR is unnecessary and does not directly address the issue, yet it introduces unintended side effects.\n\n",[2965],{"name":2879,"color":2889},3367,"PR 2600 redraws entire table introducing performance and usability issues","2025-03-08T12:13:14Z","https://github.com/nuxt/ui/issues/3367",0.7883055,["Reactive",2972],{},["Set"],["ShallowReactive",2975],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fZrAgSjxyw4Y87GEAGa6bdywtpqxC7QX6DAwQpEmSLhA":-1},"/nuxt/ui/4145"]