\n\nBrowser: `Google Chrome Version 134.0.6998.89 (Official Build) (arm64)`\n\nAlso reproduced on `Safari Version 18.3.1 (20620.2.4.11.6)`\n\n### Description\n\nUser may want to copy the text in the query input of a `select-menu` component by moving cursor around text, now it's unable to do it without a keyboard (`Shift + left/right arrow` or `Cmd/Ctrl + A` to select all).\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2024,2025],{"name":1985,"color":1986},{"name":1988,"color":1989},3583,"Accessibility: unable to select text in the query input of a select-menu","2025-03-17T00:34:07Z","https://github.com/nuxt/ui/issues/3583",0.7414985,{"description":2032,"labels":2033,"number":2034,"owner":1991,"repository":2002,"state":2035,"title":2036,"updated_at":2037,"url":2038,"score":2039},"i get icon is not found locally , render mode : css\r\n\r\n\r\n",[],194,"closed","[Icon] Collection [ any Collection name ] is not found locally , while i installed @iconify/json","2024-07-20T22:05:41Z","https://github.com/nuxt/icon/issues/194",0.45013133,{"description":2041,"labels":2042,"number":2049,"owner":1991,"repository":1991,"state":2035,"title":2050,"updated_at":2051,"url":2052,"score":2053},"### Environment\n\nNuxi 3.0.0 \r\nNuxt project info: \r\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v18.12.1`\r\n- Nuxt Version: `3.0.0`\r\n- Nitro Version: `1.0.0`\r\n- Package Manager: `npm@8.19.2`\r\n- Builder: `vite`\r\n- User Config: `runtimeConfig`, `app`, `components`, `css`, `build`, `modules`, `apollo`, `postcss`, `vite`\r\n- Runtime Modules: `@nuxtjs/tailwindcss@6.1.3`, `@nuxtjs/apollo@5.0.0-alpha.4`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\n-\n\n### Describe the bug\n\nWhen using `meta` inside the `nuxt.config.ts` and using `\u003CMeta>` inside a page, both meta tags get rendered server side. This makes the google bot only read the first meta description inside the generated html. \r\n\r\nExample: \r\n`nuxt.config.ts`\r\n````ts\r\nexport default defineNuxtConfig({\r\n app: {\r\n head: {\r\n htmlAttrs: {\r\n lang: 'de',\r\n },\r\n title: 'default title',\r\n meta: [\r\n { charset: 'utf-8' },\r\n {\r\n name: 'viewport',\r\n content: 'width=device-width, initial-scale=1',\r\n },\r\n {\r\n name: 'description',\r\n content: 'default description',\r\n },\r\n ],\r\n },\r\n },\r\n});\r\n````\r\n`app.vue`\r\n\r\n````vue\r\n\u003Ctemplate>\r\n \u003CTitle>the REAL title\u003C/Title>\r\n \u003CMeta\r\n name=\"description\"\r\n content=\"the REAL description\" />\r\n \u003Cdiv>\u003Ch1>some content\u003C/h1>\u003C/div>\r\n\u003C/template>\r\n````\r\nWhen disabling JavaScript inside the browser, this is the result: \r\n\r\n\r\n\r\nAs we can see, the title gets changed correctly. But not the meta description. It gets douplicated. \r\n\r\nThe expected behaviour would be, that the custom meta description from the page should be rendered. \n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2043,2046],{"name":2044,"color":2045},"3.x","29bc7f",{"name":2047,"color":2048},"pending triage","E99695",19186,"Double meta description when using meta inside nuxt config and meta component inside page","2023-02-21T10:09:43Z","https://github.com/nuxt/nuxt/issues/19186",0.66870296,{"description":2055,"labels":2056,"number":2062,"owner":1991,"repository":1991,"state":2035,"title":2063,"updated_at":2064,"url":2065,"score":2066},"I noticed that meta tags in a page component don't automatically overwrite (or, more specifically, replace) meta tags in the nuxt.config.js.\r\n\r\nFor example: ```nuxt.config.js```:\r\n\r\n```\r\n...head: {\r\n title: 'starter',\r\n meta: [\r\n { charset: 'utf-8' },\r\n { name: 'viewport', content: 'width=device-width, initial-scale=1' },\r\n { name: 'keywords', content: 'keyword 1, keyword 2'},\r\n {name: 'description', content: 'This is the generic description.'}\r\n\r\n ],\r\n },\r\n...\r\n```\r\n\r\nHowever, if I also have a ```description``` meta in my individual page:\r\n\r\n```\r\nexport default {\r\n head () {\r\n return {\r\n title: `Page 1 (${this.name}-side)`,\r\n meta: [\r\n { name: 'description', content: \"Page 1 description\" }\r\n ],\r\n }\r\n }\r\n}\r\n```\r\n\r\nI notice that two meta tags with description are generated. I assume this is by design. But is there a way to have a default description replaced -- overwritten -- by a page-level description?\r\n\r\nI ask because I'm trying to essentially replace Jekyll with Nuxt -- via ```nuxt generate``` -- and then have a json file generated (via Cheerio parsing the generated pages) with all the meta tags that, in turn, can be fetched back into the home page to display the recent posts (including, as I indicate above, the meta descriptions for each page.)\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/c96\">#c96\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2057,2059],{"name":2011,"color":2058},"cc317c",{"name":2060,"color":2061},"2.x","d4c5f9",117,"Meta tags duplicated","2023-01-18T15:38:30Z","https://github.com/nuxt/nuxt/issues/117",0.68063104,{"description":2068,"labels":2069,"number":2074,"owner":1991,"repository":1992,"state":2035,"title":2075,"updated_at":2076,"url":2077,"score":2078},"### Description\n\nJust tried to implement my first form that does some smaller frontend validation and sends the payload to an API that will escalate errors as well.\n\nGoing through all the use cases, some are rather hard and cumbersome to implement:\n\n- Field validation errors are fine\n- Form errors require a field to work, there is no way to define Form wide errors through `Form.setErrors()` nor do they bubble up to a general error display just where the `\u003CUForm />` is anchored if the key is unknown.\n- The missing error bubbeling makes it tricky to react to more common errors like rate limiting through 429 status code, where the server responds with additional headers and maybe a JSON with further information. This creates a hard coupling of the loose backend error message and a hard field within the current form to route the error to.\n\nAlso the submission event `FormSubmitEvent` could offer better developer experience by offering not only data, but the actual Form instance. Right now, to handle any errors by a backend, you need to go through the typical, type-messy approach of\n\n```ts\n\u003Ctemplate>\n \u003CUForm ref=\"form\" @submit=\"onSubmit\" />\n\u003C/template>\n\n\u003Cscript lang=\"ts\" setup>\ntype FormSchema = v.InferOutput\u003Ctypeof CreateSomethingForm>\n\nconst form = useTemplateRef\u003CForm\u003CFormSchema>>('form')\n\nasync function onSubmit(event: FormSubmitEvent\u003CFormSchema>) {\n\n form.value?.setErrors([\n {name: 'account', message: 'Not valid'}\n ])\n}\n\u003C/script>\n```\n\ninstead of a simpler boilerplate:\n\n```ts\n\u003Ctemplate>\n \u003CUForm @submit=\"onSubmit\" />\n\u003C/template>\n\n\u003Cscript lang=\"ts\" setup>\ntype FormSchema = v.InferOutput\u003Ctypeof CreateSomethingForm>\n\nasync function onSubmit(event: FormSubmitEvent\u003CformSchema>) {\n event.form.setErrors([\n {name: 'account', message: 'Not valid'}\n ])\n}\n\u003C/script>\n```\n\n\n\n\n### Additional context\n\n_No response_",[2070,2073],{"name":2071,"color":2072},"enhancement","a2eeef",{"name":2014,"color":2015},3471,"Form improvements","2025-03-12T08:31:46Z","https://github.com/nuxt/ui/issues/3471",0.6982059,{"description":2080,"labels":2081,"number":2086,"owner":1991,"repository":1992,"state":2035,"title":2087,"updated_at":2088,"url":2089,"score":2090},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.2.0\n- Nuxt Version: 3.14.159\n- CLI Version: 3.15.0\n- Nitro Version: -\n- Package Manager: pnpm@9.1.1\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/eslint@0.6.1, @nuxt/ui@2.19.2, nuxt-svgo@4.0.8\n- Build Modules: -\n\n### Version\n\nv2.19.2 - pro v1.5\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-qvnuqy?file=app.vue\n\n### Description\n\nI'd like to change the color of the badge in the `DashboardSidebarLinks` to be `red`.\nin the [config page ](https://ui.nuxt.com/pro/components/dashboard-sidebar-links#config) the ui config for the badge is there with the color key, but when i try to use set the color as red, typescript says `Type '\"red\"' is not assignable to type '\"gray\"'`. \nIn the component file, color values (and other values) are marked as const; is this intentional? \nIf so why the config in the docs? \n\nHappy to provide a pr removing the `as const` if it's just an error.\n\nThanks\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2082,2083],{"name":1985,"color":1986},{"name":2084,"color":2085},"pro","5BD3CB",2695,"[pro]DashboardSidebarLinks typescript errors","2024-12-06T10:44:23Z","https://github.com/nuxt/ui/issues/2695",0.71177816,{"description":2092,"labels":2093,"number":2094,"owner":1991,"repository":2002,"state":2035,"title":2095,"updated_at":2096,"url":2097,"score":2098},"My folder structure looks the same as it is described in the documentation (https://nuxt.com/modules/icon#custom-local-collections):\n\n`assets/my-icons/photogrammetry.svg`\n\nHowever, I load content from a json file:\n\n```json\n{\n \"data\": {\n \"0\": {\n \"title\": \"Video- & Photography\",\n \"icon\": \"my-icon:photogrammetry\",\n \"iconColor\": \"text-cyan-400\",\n [...]\n },\n```\n\n... into the component:\n\n```vue\n\u003Cscript setup>\nimport services from \"/public/jsons/services.json\"\n...\n\u003C/script>\n\n\u003Ctemplate>\n[...]\n \u003Cdiv class=\"[ card ] absolute\" :class=\"service.iconColor\">\n \u003CIcon :name=\"service.icon\" :color=\"service.iconColor\" size=\"10rem\" />\n \u003C/div>\n[...]\n\u003C/template>\n```\n\nThe icon (which is and remains black) does not accept any color, while any standard implementation (icon from a downloaded icon set like mdi) does indeed change the color of an icon.\n\n(Just in case this is not an error: What kind of \"treatment\" do I have to apply to make my icon accept color?)",[],307,"custom local collections do not accept props like color","2024-11-23T10:19:42Z","https://github.com/nuxt/icon/issues/307",0.7290353,["Reactive",2100],{},["Set"],["ShallowReactive",2103],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"6JmgjrO_EJm60PTKtS9zncJIY0X-2lIhoptFL4eMf_E":-1},"/nuxt/scripts/194"]