\n```\n\nsame result is expected when using `active`, but `leadingIcon` is ignored\n```\n\u003CUButton\n label=\"Label\"\n active\n active-color=\"primary\"\n active-variant=\"soft\"\n icon=\"mdi-account\"\n @click.prevent=\"active = !active\"\n/>\n```\n\n### Additional context\n\n\u003Cimg width=\"202\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/0756fb1c-772c-44ae-855d-90aba304bd9e\" />",[2924,2927,2928],{"name":2925,"color":2926},"bug","d73a4a",{"name":2908,"color":2909},{"name":2911,"color":2912},3972,"Different result than static for active-color & active-variant","2025-04-24T15:30:39Z","https://github.com/nuxt/ui/issues/3972",0.77854663,{"description":2935,"labels":2936,"number":2937,"owner":2914,"repository":2938,"state":2939,"title":2940,"updated_at":2941,"url":2942,"score":2943},"We’ve consistently ran into issues with hydration and `useId` across some Nuxt projects and I think we finally found the culprit. I've forked the example from https://github.com/nuxt/icon/issues/310 and slightly altered it to reproduce the issue. Both `svg` and `css` mode lead to the error. Might it be related to the custom api endpoint?\n\n```\n[Vue warn]: Hydration attribute mismatch on \u003Cinput id=\"v-1-0\"> \n - rendered on server: id=\"v-1-0\"\n - expected on client: id=\"v-0-0\"\n Note: this mismatch is check-only. The DOM will not be rectified in production due to performance overhead.\n You should fix the source of the mismatch. \n at \u003CCustomInput> \n at \u003CTestComponent> \n at \u003CApp key=4 > \n at \u003CNuxtRoot>\n```\n\nThe reproduction can be found here:\nhttps://stackblitz.com/edit/github-pz2kcg-jtmax8ot?file=nuxt.config.ts",[],356,"icon","closed","Hydration mismatch with useId() if \u003CIcon /> is used","2025-04-10T06:07:28Z","https://github.com/nuxt/icon/issues/356",0.47143102,{"description":2945,"labels":2946,"number":2937,"owner":2914,"repository":2948,"state":2939,"title":2949,"updated_at":2950,"url":2951,"score":2943},"### 🐛 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_",[2947],{"name":2925,"color":2926},"scripts","error loading dynamically imported module, when using adsense script","2025-02-12T08:39:18Z","https://github.com/nuxt/scripts/issues/356",{"description":2953,"labels":2954,"number":2957,"owner":2914,"repository":2958,"state":2939,"title":2959,"updated_at":2960,"url":2961,"score":2962},"",[2955],{"name":2905,"color":2956},"1ad6ff",277,"nuxt.com","Command palettes modals should always have first element selected","2023-02-15T12:32:03Z","https://github.com/nuxt/nuxt.com/issues/277",0.6880224,{"description":2964,"labels":2965,"number":2957,"owner":2914,"repository":2966,"state":2939,"title":2967,"updated_at":2968,"url":2969,"score":2962},"https://github.com/nuxt-community/laravel-echo-module/blob/main/test/basic.test.ts#L12",[],"test-utils","renderAndGetWindow type not found","2023-12-02T00:13:07Z","https://github.com/nuxt/test-utils/issues/277",{"description":2971,"labels":2972,"number":2976,"owner":2914,"repository":2915,"state":2939,"title":2977,"updated_at":2978,"url":2979,"score":2980},"### 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```",[2973,2974,2975],{"name":2925,"color":2926},{"name":2908,"color":2909},{"name":2911,"color":2912},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.72318625,{"description":2982,"labels":2983,"number":2986,"owner":2914,"repository":2958,"state":2939,"title":2987,"updated_at":2988,"url":2989,"score":2990},"Those files should also have the same design as in the tree:\n\n\n",[2984],{"name":2925,"color":2985},"ff281a",218,"Prevent select of deleted files in command palette","2022-03-29T10:23:59Z","https://github.com/nuxt/nuxt.com/issues/218",0.7530223,{"description":2992,"labels":2993,"number":2986,"owner":2914,"repository":2948,"state":2939,"title":2995,"updated_at":2996,"url":2997,"score":2990},"### 🆒 Your use case\r\n\r\nFor scripts using the default trigger (onNuxtReady) we should probably do a prefetch or preload so that the script is downloaded and executated as quickly as possible.\r\n\r\n### 🆕 The solution you'd like\r\n\r\n-\r\n\r\n### 🔍 Alternatives you've considered\r\n\r\n_No response_\r\n\r\n### ℹ️ Additional info\r\n\r\n_No response_",[2994],{"name":2905,"color":2906},"DNS prefetch / preload default triggered scripts","2024-09-27T08:15:47Z","https://github.com/nuxt/scripts/issues/218",{"description":2999,"labels":3000,"number":3007,"owner":2914,"repository":2914,"state":2939,"title":3008,"updated_at":3009,"url":3010,"score":3011},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v18.18.2`\r\n- Nuxt Version: `3.6.1`\r\n- Nitro Version: `2.5.2`\r\n- Package Manager: `npm@9.8.1`\r\n- Builder: `vite`\r\n- User Config: `ssr`, `nitro`, `app`, `modules`, `security`, `vite`\r\n- Runtime Modules: `nuxt-security@1.0.0-rc.2`, `nuxt-vitest@0.10.2`\r\n- Build Modules: `-`\r\n\r\n\r\nAlthough we are pinned at Nuxt v3.6.1 'for reasons' the bug can be observed in StackBlitz repro on Nuxt v3.8.2\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-6rrfcj?file=pages%2Findex.vue\r\n\r\nNote: Issue relates to keyboard navigation! - not mouse.\r\n\r\n- Open `index` page and tab bring focus to button labelled `Goto Two`. \r\n- Hit enter key to effectively `click` button. (remember, keyboard - not mouse!)\r\n- Browser navigates to page `two`\r\n\r\nNotice the header suggests that the function `handleNext` has been called. This suggest that the `@keyup` event has fired on the `input` control on page `two` as `handleNext` is the function handling of that event. I can't think why this should be expected behaviour. Almost as if the `keyup` event from pressing the button on the `index` page is being seen by page `two` when the `focus()` call is made?! \r\n\r\nOpen the browser devtools to see console.log messages also indicating that `handleNext` has been called.\r\n\r\nAlso, to add additional context/relevant to help diagnose the error. In the script for `two.vue` there is another option (2) that can be uncommented and option (1) commented out. This only calls `focus()` after a delay. With this in place the potential bug doesn't happen.\r\n\r\n### Describe the bug\r\n\r\nI'm seeing what I think maybe a bug when navigating to a page that combines and `input` control with an associated `@keyup` handler that is also focused on page load via `onMounted` lifecycle event.\r\n\r\nFollow the reproduction above and also the effect of delaying the call to `focus()` on the `input` control.\r\n\r\n\r\n### Additional context\r\n\r\nChanging the event type on the `input` field from `@keyup` to `@keydown` also avoids the issue.\r\n\r\n### Logs\r\n\r\n_No response_",[3001,3004],{"name":3002,"color":3003},"3.x","29bc7f",{"name":3005,"color":3006},"pending triage","E99695",24434,"Unexpected @keyup triggering on focused input field when navigated to via keyboard \"click\"","2023-11-28T14:35:12Z","https://github.com/nuxt/nuxt/issues/24434",0.75664043,["Reactive",3013],{},["Set"],["ShallowReactive",3016],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f5EWLuknqJjPdRhRjll8blEx3691UHOseqvee0cKS_DU":-1},"/nuxt/nuxt.com/356"]