\n \u003CUInput v-model=\"state.name1\" placeholder=\"...\" />\n\u003C/UModal>\n```\n\nWhen a modal contains one or more input boxes, the first input box will always get focus automatically.\nIf I manually add a close button in the upper right corner, it will trigger a validation when I click it. This is not good. How can I avoid the input box getting focus when opening the modal?\n\n### Additional context\n\n\n\n\n### Logs\n\n```shell-script\n\n```",[2004,2005],{"name":1985,"color":1986},{"name":1991,"color":1992},3062,"The input box in the modal will automatically gain focus","2025-01-10T08:36:56Z","https://github.com/nuxt/ui/issues/3062",0.6274172,{"description":2012,"labels":2013,"number":2015,"owner":1994,"repository":2016,"state":1996,"title":2017,"updated_at":2018,"url":2019,"score":2020},"### 🐛 The bug\n\nThe center marker is always show on maps placeholder image.\nSee https://github.com/nuxt/scripts/blob/f96f7b51549f302160559041bbf056589e899b04/src/runtime/components/ScriptGoogleMaps.vue#L394\n\n### 🛠️ To reproduce\n\nttps://stackblitz.com/edit/nuxt-starter-pkwfkx?file=pages%2Findex.vue\n\n### 🌈 Expected behavior\n\nShould be dependent on centerMarker boolean prop: https://github.com/nuxt/scripts/blob/f96f7b51549f302160559041bbf056589e899b04/src/runtime/components/ScriptGoogleMaps.vue#L60\n\n### ℹ️ Additional context\n\n_No response_",[2014],{"name":1985,"color":1986},402,"scripts","Center marker always shown on maps placeholder image","2025-02-24T14:10:21Z","https://github.com/nuxt/scripts/issues/402",0.6298097,{"description":2022,"labels":2023,"number":2024,"owner":1994,"repository":2025,"state":1996,"title":2026,"updated_at":2027,"url":2028,"score":2029},"My icon file directory is nested, which means I'm creating multiple `customCollections`, like this: \n\n\nIs there a simpler way to write it?",[],316,"icon","Local custom nested folder usage issues","2025-03-16T06:02:57Z","https://github.com/nuxt/icon/issues/316",0.66883534,{"description":2031,"labels":2032,"number":2015,"owner":1994,"repository":2036,"state":2037,"title":2038,"updated_at":2039,"url":2040,"score":2020},"Redirect to `/projects` public page instead\n\nBlocked by #403 ",[2033],{"name":2034,"color":2035},"enhancement","1ad6ff","nuxt.com","closed","Beta page integration `/beta`","2022-06-07T09:41:42Z","https://github.com/nuxt/nuxt.com/issues/402",{"description":2042,"labels":2043,"number":2047,"owner":1994,"repository":1995,"state":2037,"title":2048,"updated_at":2049,"url":2050,"score":2051},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.x\n\n### Description\n\nAs of now, in Nuxt UI v3.0.0-alpha.x, the `SIDE_OPTIONS` constant is defined as follows:\n\n``` ts\nconst SIDE_OPTIONS: [\"top\", \"right\", \"bottom\", \"left\"];\n```\n\nThe current four directions cannot meet the practical development needs. For example, when there is a button on the far right of the screen to open a dropdown menu, it cannot automatically appear as 'bottom-right'.Tooltips, dropdown menus, or popovers may require positioning beyond the basic cardinal directions to avoid obscuring content or to better fit within the viewport.\n\n#### Proposed Enhancement\n\nI propose to extend the SIDE_OPTIONS constant to include combinations of the cardinal directions to allow for greater flexibility and finer control over positioning. The updated SIDE_OPTIONS would be:\n\n``` ts\nconst SIDE_OPTIONS = [\n \"top\", \"right\", \"bottom\", \"left\",\n \"bottom-left\", \"bottom-right\",\n \"left-top\", \"left-bottom\",\n \"top-left\", \"top-right\",\n \"right-top\", \"right-bottom\"\n];\n```\n\n\n### Additional context\n\n| | |\n| ----------- | ----------- |\n|  | |\n\n\n",[2044,2046],{"name":2034,"color":2045},"a2eeef",{"name":1988,"color":1989},2712,"Side needs more direction","2024-11-20T19:59:29Z","https://github.com/nuxt/ui/issues/2712",0.6476987,{"description":2053,"labels":2054,"number":2060,"owner":1994,"repository":1995,"state":2037,"title":2061,"updated_at":2062,"url":2063,"score":2064},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.11.0\n- Nuxt Version: 3.16.0\n- CLI Version: 3.22.5\n- Nitro Version: 2.11.6\n- Package Manager: pnpm@9.15.4\n- Builder: -\n- User Config: modules, devtools, app, css, runtimeConfig, future, compatibilityDate, telemetry, eslint\n- Runtime Modules: @nuxt/ui-pro@3.0.0, @nuxt/eslint@1.0.1, @vueuse/nuxt@12.5.0, @nuxt/image@1.9.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3\n\n### Reproduction\n\nSee below\n\n### Description\n\nHey,\n\nIn UI2 when placing a UAvatar (which often is done for a user dropdown) in the DropdownMenu - clicking the Dropdown menu would trigger opening the dropdown.\nBased on UI3 docs it seems that it should work since it says Button or any other element - however this doesnt work\n\n### Additional context\n\n```ts\n\u003CUDropdownMenu :items=\"accountItems\">\n \u003CUAvatar\n v-if=\"session && session.user\"\n :src=\"session.user.image ? session.user.image : undefined\"\n :alt=\"session.user.name\"\n size=\"md\"\n />\n\u003C/UDropdownMenu>\n```\n\n### Logs\n\n```shell-script\n\n```",[2055,2056,2059],{"name":1985,"color":1986},{"name":2057,"color":2058},"needs reproduction","CB47CF",{"name":1988,"color":1989},3546,"`UAvatar` doesn't trigger `UDropdownMenu`","2025-03-28T17:43:01Z","https://github.com/nuxt/ui/issues/3546",0.66775715,{"description":2066,"labels":2067,"number":2069,"owner":1994,"repository":2016,"state":2037,"title":2070,"updated_at":2071,"url":2072,"score":2073},"### 🐛 The bug\n\n> You are correct $script.remove() works but still requires the $script.entry = undefined; if you ever wanted to reload the script.\n\n### 🛠️ To reproduce\n\n-\n\n### 🌈 Expected behavior\n\n-\n\n### ℹ️ Additional context\n\n_No response_",[2068],{"name":1985,"color":1986},334,"Removing a script won't let you reload it","2024-12-08T02:26:36Z","https://github.com/nuxt/scripts/issues/334",0.66963804,{"description":2075,"labels":2076,"number":2077,"owner":1994,"repository":2036,"state":2037,"title":2078,"updated_at":2079,"url":2080,"score":2081},"Multiple links in showcase links to either dead sites or dead pages on the sites. I have attached a few. Also the russian mcdonalds site is on there\r\nhttps://mcdonalds.ru/\r\nhttps://ai.marketing/user/robot\r\nhttps://game.fonts.adobe.com/\r\nhttps://annual.awwwards.com/\r\nhttps://globalmaintainersummit.github.com/\r\nhttps://vintageria.it/\r\nhttps://hyundaiusa.com/",[],1530,"Dead showcase links","2024-03-11T22:26:22Z","https://github.com/nuxt/nuxt.com/issues/1530",0.6737013,{"description":2083,"labels":2084,"number":2091,"owner":1994,"repository":1994,"state":2037,"title":2092,"updated_at":2093,"url":2094,"score":2095},"### Environment\r\n\r\n```\r\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v16.14.2`\r\n- Nuxt Version: `3.0.0`\r\n- Nitro Version: `1.0.0`\r\n- Package Manager: `npm@7.17.0`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\r\n```\r\n\r\n### Reproduction\r\n\r\nHere is a minimal reproduction:\r\n[https://stackblitz.com/edit/github-u8yyoy?file=app.vue](https://stackblitz.com/edit/github-u8yyoy?file=app.vue)\r\n\r\n### Describe the bug\r\n\r\n`v-model` is behaving weirdly when a value is already set while mounting the component.\r\n\r\nIn the following example the select box initially shows option `A` then the Component re-renders and shows the correct option `B`. However the selected ref is set to `3` from the beginning according to the output in the console when I'm logging the `selected` ref.\r\n\r\n``` vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Cselect v-model=\"selected\">\r\n \u003Coption value=\"2\">A\u003C/option>\r\n \u003Coption value=\"3\">B\u003C/option>\r\n \u003Coption value=\"4\">C\u003C/option>\r\n \u003C/select>\r\n \u003C/div>\r\n\u003C/template>\r\n\u003Cscript setup lang=\"ts\">\r\nimport { ref } from 'vue';\r\nconst selected = ref('3');\r\n\u003C/script>\r\n```\r\n\r\nWhen using the `v-bind` directive and `@change`, everything works fine.\r\n\r\n``` vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Cselect @change=\"(e) => selectedValue = e.target.value\">\r\n \u003Coption value=\"4\" :selected=\"isSelected('4')\">A\u003C/option>\r\n \u003Coption value=\"5\" :selected=\"isSelected('5')\">B\u003C/option>\r\n \u003Coption value=\"6\" :selected=\"isSelected('6')\">C\u003C/option>\r\n \u003C/select>\r\n \u003C/div>\r\n\u003C/template>\r\n\u003Cscript setup lang=\"ts\">\r\nimport { ref } from 'vue';\r\nconst selected = ref('6');\r\nconst isSelected = (value) => selectedValue.value === value\r\n\u003C/script>\r\n```\r\n\r\nMoreover, this error occurs only when using a select box. Other types of input fields (checkbox, radio button, text input) work. Also when doing the same in plain Vue 3 it works.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2085,2088],{"name":2086,"color":2087},"3.x","29bc7f",{"name":2089,"color":2090},"upstream","E8A36D",15631,"Select box with v-model updates lazy when mounting the component","2023-01-19T18:30:04Z","https://github.com/nuxt/nuxt/issues/15631",0.67810667,["Reactive",2097],{},["Set"],["ShallowReactive",2100],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"Q4KxInEVnbzxzZE-GQ0xvsbgZRpf0bmW9MXA9ielnOY":-1},"/nuxt/ui/3635"]