is used","2025-04-10T06:07:28Z","https://github.com/nuxt/icon/issues/356",0.75651556,{"description":3041,"labels":3042,"number":3033,"owner":3023,"repository":3045,"state":3035,"title":3046,"updated_at":3047,"url":3048,"score":3039},"I suppose this is related to how we selected the first element",[3043],{"name":3020,"color":3044},"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":3050,"labels":3051,"number":3033,"owner":3023,"repository":3024,"state":3035,"title":3053,"updated_at":3054,"url":3055,"score":3039},"### 🐛 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_",[3052],{"name":3020,"color":3021},"error loading dynamically imported module, when using adsense script","2025-02-12T08:39:18Z","https://github.com/nuxt/scripts/issues/356",{"description":3057,"labels":3058,"number":3065,"owner":3023,"repository":3023,"state":3035,"title":3066,"updated_at":3067,"url":3068,"score":3069},"### 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>",[3059,3062],{"name":3060,"color":3061},"question","cc317c",{"name":3063,"color":3064},"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.777072,{"description":3071,"labels":3072,"number":3078,"owner":3023,"repository":3079,"state":3035,"title":3080,"updated_at":3081,"url":3082,"score":3083},"### 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_",[3073,3075],{"name":3060,"color":3074},"d876e3",{"name":3076,"color":3077},"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":3085,"labels":3086,"number":3092,"owner":3023,"repository":3079,"state":3035,"title":3093,"updated_at":3094,"url":3095,"score":3096},"### 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```",[3087,3088,3089],{"name":3020,"color":3021},{"name":3076,"color":3077},{"name":3090,"color":3091},"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":3098,"labels":3099,"number":3103,"owner":3023,"repository":3045,"state":3035,"title":3104,"updated_at":3105,"url":3106,"score":3107},"",[3100],{"name":3101,"color":3102},"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":3109,"labels":3110,"number":3103,"owner":3023,"repository":3111,"state":3035,"title":3112,"updated_at":3113,"url":3114,"score":3107},"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":3116,"labels":3117,"number":3122,"owner":3023,"repository":3079,"state":3035,"title":3123,"updated_at":3124,"url":3125,"score":3126},"### Description\n\nI would like to be able to focus on the input in an InputMenu using a keyboard shortcut. This is already possible for the UInput (https://ui.nuxt.com/components/input#with-keyboard-shortcut), but the focus function is not exposed for UInputMenu.\n\n```\nconst input = useTemplateRef('input')\n\ndefineShortcuts({\n '/': () => {\n input.value?.inputRef?.focus()\n }\n})\n```\n\n### Additional context\n\n_No response_",[3118,3120,3121],{"name":3101,"color":3119},"a2eeef",{"name":3076,"color":3077},{"name":3090,"color":3091},4450,"UInputMenu focus with keyboard shortcut","2025-07-03T15:23:10Z","https://github.com/nuxt/ui/issues/4450",0.7874157,["Reactive",3128],{},["Set"],["ShallowReactive",3131],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fZrAgSjxyw4Y87GEAGa6bdywtpqxC7QX6DAwQpEmSLhA":-1},"/nuxt/ui/4145"]