\r\n\r\n \u003Cdiv>\u003CNuxtLink to=\"/\">HOME\u003C/NuxtLink>\u003C/div>\r\n \u003Cdiv>\u003CNuxtLink to=\"/?name=roro\">/?name=roro\u003C/NuxtLink>\u003C/div>\r\n \u003Cdiv>\u003CNuxtLink to=\"/about\">About\u003C/NuxtLink>\u003C/div>\r\n\r\n \u003Cul>\r\n \u003Cli>Enter a name in the input field above\u003C/li>\r\n \u003Cli>Click on the ?name=roro link\u003C/li>\r\n \u003Cli>Click on the HOME link\u003C/li>\r\n \u003Cli>The page should be re-rendered and reset but it's not happening. The input should be cleared.\u003C/li>\r\n \u003C/ul>\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript setup lang=\"ts\">\r\n const route = useRoute()\r\n\r\n onBeforeRouteUpdate(to => {\r\n // Refresh the page (not hard refresh)!\r\n if (to.fullPath === '/') {\r\n route.meta.pageKey = 'test'\r\n\r\n document.querySelector('#logs')!.textContent = document.querySelector('#logs')!.textContent + 'Changing page key, it should re-render the page and clear all data...'\r\n }\r\n })\r\n\r\n definePageMeta({ key: (route) => route.meta.pageKey })\r\n\u003C/script>\r\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[1984],{"name":1985,"color":1986},"pending triage","E99695",28086,"nuxt","open","Changing `key` on page does not re-render it","2024-08-28T20:39:13Z","https://github.com/nuxt/nuxt/issues/28086",0.7242763,{"description":1995,"labels":1996,"number":2003,"owner":1988,"repository":2004,"state":1989,"title":2005,"updated_at":2006,"url":2007,"score":2008},"### Description\r\n\r\n**Problem**\r\nThe current implementation of the keyboard shortcuts composable (defineShortcuts) doesn't work correctly with non-Latin keyboard layouts, such as Arabic. This limits the usability of the composable for users with different language settings.\r\n\r\n**Proposed Solution**\r\nImplement an optional configuration flag '_layoutIndependent_' that, when set to true, makes the composable use KeyboardEvent.code instead of KeyboardEvent.key. This change will allow the shortcuts to work regardless of the keyboard layout or language setting.\r\n\r\n### Additional context\r\n\r\n_No response_",[1997,2000],{"name":1998,"color":1999},"enhancement","a2eeef",{"name":2001,"color":2002},"triage","ffffff",2293,"ui","Add support for non-Latin keyboard layouts in defineShortcuts composable","2025-01-10T07:47:55Z","https://github.com/nuxt/ui/issues/2293",0.72927994,{"description":2010,"labels":2011,"number":2016,"owner":1988,"repository":2004,"state":1989,"title":2017,"updated_at":2018,"url":2019,"score":2020},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v20.18.0\n- Nuxt Version: 3.11.2\n- CLI Version: 3.15.0\n- Nitro Version: 2.9.6\n- Package Manager: pnpm@9.5.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxtjs/i18n@8.0.0, @nuxt/ui@2.16.0, @nuxtjs/tailwindcss@6.12.0, @pinia/nuxt@0.5.1, @nuxtjs/google-fonts@3.2.0, @nuxtjs/eslint-module@4.1.0, @nuxt/test-utils/module@3.13.1\n- Build Modules: -\n------------------------------\n\n\n\n### Version\n\nv.2.15.0\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-1f7znf?file=app.vue,nuxt.config.ts\n\n### Description\n\nWhen providing custom animations through tailwindcss config, some Nuxt UI animations stop working. I have provided an example of a `UButton` with `loading` set in the repro link above.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2012,2015],{"name":2013,"color":2014},"bug","d73a4a",{"name":2001,"color":2002},2732,"Adding custom animations disable Nuxt UI ones","2024-11-22T15:38:35Z","https://github.com/nuxt/ui/issues/2732",0.7384179,{"description":2022,"labels":2023,"number":2029,"owner":1988,"repository":2004,"state":1989,"title":2030,"updated_at":2031,"url":2032,"score":2033},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.x\n\n### Description\n\nHello everyone, I’d like to discuss the possibility of setting `props` by default from `AppConfig`. Currently, it’s very convenient that we can configure the theme through the config. It would be great to have a similar option for props. Previously, @benjamincanac mentioned [here](https://github.com/nuxt/ui/issues/1289#issuecomment-2480556540) that this is not currently planned.\n\nMy proposal is simple: wrap all `withDefaults` in our own implementation. This way, we can define props without making significant changes to the code.\n\n## What it could look like\n\nLet’s look at the `Accordion.vue` component. At the moment, its props look like this:\n```ts\nconst props = withDefaults(defineProps\u003CAccordionProps\u003CT>>(), {\n type: 'single',\n collapsible: true,\n labelKey: 'label'\n})\n```\nLet’s assume our wrapper is called `withUiDefaults`. Then the code would look like this:\n```diff\n-const props = withDefaults(defineProps\u003CAccordionProps\u003CT>>(), {\n+const props = withUiDefaults(defineProps\u003CAccordionProps\u003CT>>(), {\n type: 'single',\n collapsible: true,\n labelKey: 'label'\n})\n```\nThe implementation of `withUiDefaults` is quite simple:\n```ts\nfunction withUiDefaults(props, defaults) {\n const defaultFromConfig = {}\n\n return withDefaults(props, {\n ...defaults,\n ...defaultFromConfig\n })\n}\n``` \n\n## Issues I See\n\n1) **Typing `AppConfig` might be challenging** \n We would need to somehow generate types based on the components. \n **My opinion:** I think we can retrieve this using `vue-component-meta` during the UI build stage. So, in my opinion, this isn’t a significant problem.\n\n2) **Developers might set `modelValue` or other critical props by default** \n **My opinion:** In such cases, we can log a warning to the console. Additionally, developers should understand which props they are overriding. We won’t be able to cover all edge cases, but I don’t think we need to.\n\n### Additional context\n\n_No response_",[2024,2025,2028],{"name":1998,"color":1999},{"name":2026,"color":2027},"v3","49DCB8",{"name":2001,"color":2002},2662,"Override default props from `AppConfig`","2024-11-17T08:30:46Z","https://github.com/nuxt/ui/issues/2662",0.7390472,{"description":2035,"labels":2036,"number":2040,"owner":1988,"repository":2004,"state":2041,"title":2042,"updated_at":2043,"url":2044,"score":2045},"### Environment\n\n- Operating System: Windows 10 \n- Node Version: v22.10.0 \n- Nuxt Version: 3.16.0 \n- CLI Version: 3.22.5 \n- Nitro Version: 2.11.5 \n- Package Manager: pnpm@9.15.7 \n- Builder: -\n- User Config: compatibilityDate, devtools, modules, css, meta, ssr, runtimeConfig, ui \n- Runtime Modules: @nuxt/ui@3.0.0-beta.3, @nuxt/icon@1.10.3, @nuxt/fonts@0.11.0, @vueuse/nuxt@12.8.2\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nNuxt UI 3.0\n\n### Reproduction\n\n```\n\u003Ctemplate>\n\u003CUInput\n v-model=\"translation\"\n ref=\"translationField\" \n />\n\u003C/template>\n\n\u003Cscript setup>\nconst translationField = ref(null)\n\nfunction nextCard() {\n translationField.value.focus() // throws: 'focus is not a function'\n \n nextTick(() => {\n translationField.value.focus() // same error\n })\n\n // below works ok\n nextTick(() => {\n const input = translationField.value?.$el?.querySelector('input')\n if (input) {\n input.focus()\n }\n })\n}\n\u003C/script>\n```\n\n\n### Description\nStandard Vue method of using template ref (for setting a focus, here) throws: 'focus() is not a function'\nIn the above code snippet I included workaround (credits to Sonnet 3.5)\nTried it dozen of times and checked this place to see if it has not been solved earlier.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2037,2038,2039],{"name":2013,"color":2014},{"name":2026,"color":2027},{"name":2001,"color":2002},3644,"closed","\u003CUInput> template ref does not work","2025-03-21T13:14:18Z","https://github.com/nuxt/ui/issues/3644",0.70441127,{"description":2047,"labels":2048,"number":2051,"owner":1988,"repository":2004,"state":2041,"title":2052,"updated_at":2053,"url":2054,"score":2055},"### Description\n\nThe Nuxt UI v2 dropdown has the option to open on hover or click. In v3 the only option available is click. \n\n\n\n### Additional context\n\n_No response_",[2049,2050],{"name":1998,"color":1999},{"name":2026,"color":2027},3322,"[DropdownMenu] (v3) missing mode prop for hover/click","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/3322",0.70491326,{"description":2057,"labels":2058,"number":2063,"owner":1988,"repository":2004,"state":2041,"title":2064,"updated_at":2065,"url":2066,"score":2067},"### Description\n\nHello! I'm working on a huge project that relies on Nuxt UI v2. We want to upgrade to Nuxt UI v3, but the changes are vast, and I'm wondering if it is possible to have version 2 and version 3 at the same time somehow so we can do an incremental upgrade. If it's not possible, then I would LOVE for this to be a feature request to be able to do somehow.\n\nThanks!",[2059,2062],{"name":2060,"color":2061},"question","d876e3",{"name":2026,"color":2027},3562,"Incremental upgrade possible?","2025-03-17T16:11:35Z","https://github.com/nuxt/ui/issues/3562",0.7198241,{"description":2069,"labels":2070,"number":2073,"owner":1988,"repository":2004,"state":2041,"title":2074,"updated_at":2075,"url":2076,"score":2077},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.14.0\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.7\n- Package Manager: yarn@1.22.22\n- Builder: -\n- User Config: devtools, typescript, css, compatibilityDate, devServer, vite, runtimeConfig, app, ui, modules\n- Runtime Modules: @nuxt/ui@3.0.1, @pinia/nuxt@0.10.1, pinia-plugin-persistedstate/nuxt@4.2.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.1\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/blue-wildflower-wkjpcz\n\n### Description\n\nI don't know if this issue is related to this one : https://github.com/nuxt/ui/issues/3660\n\nWhen I selects items the `@change` is triggered as expected, but when I remove items it's never triggered (while `modelValue` is updated as intended).\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2071,2072],{"name":2013,"color":2014},{"name":2026,"color":2027},3756,"InputMenu multiple doesn't emit change on item removal","2025-03-31T19:14:47Z","https://github.com/nuxt/ui/issues/3756",0.7200895,{"description":2079,"labels":2080,"number":2083,"owner":1988,"repository":2004,"state":2041,"title":2084,"updated_at":2085,"url":2086,"score":2087},"### Environment\n\n-\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.16.0\n\n### Reproduction\n\n- \n\n### Description\n\nUpgraded all deps to the latest and bam Nuxt 3.16.0 is added. We get errors now as Nuxt UI 3 still ships with\n\n`'@unhead/vue': 1.11.20(vue@3.5.13(typescript@5.8.2))\n`\n\nAs of Nuxt 3.16.0 ships with @unhead2:\nhttps://nuxt.com/blog/v3-16#unhead-v2\n\nActual error:\n`[@nuxt/scripts 9:42:20 PM] ERROR Nuxt Scripts requires Unhead >= 2, you are using v1.11.20. Please run nuxi upgrade --clean to upgrade...`\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2081,2082],{"name":2013,"color":2014},{"name":2026,"color":2027},3513,"Nuxt 3.16.0 - ships with @unhead2","2025-03-10T08:49:36Z","https://github.com/nuxt/ui/issues/3513",0.7203269,{"description":2089,"labels":2090,"number":2093,"owner":1988,"repository":2004,"state":2041,"title":2094,"updated_at":2095,"url":2096,"score":2097},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v22.13.1\n- Nuxt Version: 3.16.0\n- CLI Version: 3.22.5\n- Nitro Version: 2.11.6\n- Package Manager: pnpm@9.15.6\n- Builder: -\n- User Config: future, experimental, modules, ui, css, imports, runtimeConfig\n- Runtime Modules: @vueuse/nuxt@12.7.0, @nuxt/ui@3.0.0-beta.3, @nuxt/test-utils/module@3.16.0\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-beta.3\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/sq5zkr?file=%2Fapp.vue%3A6%2C1\n\n### Description\n\nThe issue is using a button component with the `to` attribute fails to resolve component using prefix. See [sandbox](https://codesandbox.io/p/devbox/sq5zkr?file=%2Fapp.vue%3A6%2C1)\n\n[Vue warn]: Failed to resolve component: ULinkBase\n\n```vue\n\u003CBaseButton to=\"/\">Account\u003C/BaseButton>\n```\n\noutput\n```html\n\u003Culinkbase as=\"button\" type=\"button\" href=\"/\">Account\u003Culinkbase>\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2091,2092],{"name":2013,"color":2014},{"name":2026,"color":2027},3527,"[Vue warn]: Failed to resolve component: ULinkBase","2025-03-12T13:02:20Z","https://github.com/nuxt/ui/issues/3527",0.7251447,["Reactive",2099],{},["Set"],["ShallowReactive",2102],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"dEZtp8GXBghmxI8GthCPVgSruXqIBL9IrT5PdM8fmh4":-1},"/nuxt/ui/2590"]