\r\n \u003C/UBlogList>\r\n\r\n \u003CUPagination\r\n size=\"sm\"\r\n :model-value=\"pageNum\"\r\n :total=\"maxPages\"\r\n :page-count=\"1\"\r\n show-last\r\n show-first\r\n :to=\"(page: number) => ({\r\n query: { page },\r\n // Hash is specified here to prevent the page from scrolling to the top\r\n hash: '#links',\r\n })\"\r\n @on-click-page=\"(e) => { console.log('current page', e); execute() }\"\r\n />\r\n \u003C/UPageBody>\r\n \u003C/UContainer>\r\n\u003C/template>\r\n```",[2910],{"name":2877,"color":2911},"d876e3",2190,"ui","[Pagination] emits on buttons?","2024-09-12T12:33:01Z","https://github.com/nuxt/ui/issues/2190",0.7165642,{"description":2919,"labels":2920,"number":2922,"owner":2866,"repository":2866,"state":2883,"title":2923,"updated_at":2924,"url":2925,"score":2926},"Hey,\r\nI'm working on a SSR website and keep having issues with duplicated meta tags. As you can see on the screenshot below, nuxt generate two title tags.\r\n\r\n\r\nI use nuxt `head()` method and `hid` attribute to override defaults tags on my article page, but the two meta tags are being used.\r\n\r\nIn nuxt.config.js : \r\n\u003Cimg width=\"439\" alt=\"capture d ecran 2018-02-26 a 14 24 43\" src=\"https://user-images.githubusercontent.com/4067686/36672788-e3965454-1b00-11e8-92c4-c862300de73e.png\">\r\n\r\nIn videos/_slug.vue :\r\n\u003Cimg width=\"565\" alt=\"capture d ecran 2018-02-26 a 14 22 56\" src=\"https://user-images.githubusercontent.com/4067686/36672727-a7448f98-1b00-11e8-99f5-ea1a8953654a.png\">\r\n\r\nOh, and if I remove default title and description from `nuxt.config.js`, nuxt is using the title from package.json\r\n\r\n**As anyone faced the same issue ? Or maybe I'm using nuxt head method wrong ?**\r\n\r\nThanks in advance for your help !\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/c2521\">#c2521\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2921],{"name":2880,"color":2881},2902,"Duplicated meta tags and titles","2023-01-18T16:09:43Z","https://github.com/nuxt/nuxt/issues/2902",0.7228726,{"description":2928,"labels":2929,"number":2934,"owner":2866,"repository":2913,"state":2883,"title":2935,"updated_at":2936,"url":2937,"score":2938},"### Description\n\nHey!\n\nIt would be nice to have the primary/secondary/neutral/etc colours defined in `app.config.ts` directly as tailwind variables (ex: text-primary-500)\n\nRight now we have to define the colours both in `app.config.ts` and `tailwind.config.js` to be able to do that. (the new `main.css` would require to create a variable for each sub-colour manually so not worth using it) \n\nFor `neutral`, since it's a tailwind colour, it could be named `text-neutr-500`\nOr maybe name all colours with something like `text-Uneutral-500`\n\n\n### Additional context\n\n_No response_",[2930,2931],{"name":2901,"color":2902},{"name":2932,"color":2933},"v3","49DCB8",2948,"Add theme colors as tailwind variables","2025-02-06T16:29:04Z","https://github.com/nuxt/ui/issues/2948",0.72370106,{"description":2940,"labels":2941,"number":2944,"owner":2866,"repository":2913,"state":2883,"title":2945,"updated_at":2946,"url":2947,"score":2948},"### 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_",[2942,2943],{"name":2901,"color":2902},{"name":2932,"color":2933},3471,"Form improvements","2025-03-12T08:31:46Z","https://github.com/nuxt/ui/issues/3471",0.7253979,{"description":2950,"labels":2951,"number":2957,"owner":2866,"repository":2913,"state":2883,"title":2958,"updated_at":2959,"url":2960,"score":2961},"### Description\n\nI really love all the work that went into this, but it's currently connected to vue-router for `Link` and `Pagination` components. I would love to see these become optional dependencies so it can be used with projects that do not use `vue-router`.\n\nMaybe there is some way to stub out the link components to enable support for Inertia \\ default HTML?",[2952,2953,2954],{"name":2877,"color":2911},{"name":2932,"color":2933},{"name":2955,"color":2956},"vue","42b883",3001,"How likely is it that we'll see a routerless version?","2025-04-14T08:47:28Z","https://github.com/nuxt/ui/issues/3001",0.7280552,{"description":2963,"labels":2964,"number":2972,"owner":2866,"repository":2913,"state":2883,"title":2973,"updated_at":2974,"url":2975,"score":2976},"### Environment\n\nNode 22\nNuxt 4\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0 alpha 11\n\n### Reproduction\n\nUsing a selectmenu inside a modal doesnt work with search\n\nhttps://codesandbox.io/p/devbox/objective-khayyam-kq8n74\n\n### Description\n\nOpen the modal, open the select options and you will see you cant use the search in any way\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2965,2968,2971],{"name":2966,"color":2967},"bug","d73a4a",{"name":2969,"color":2970},"duplicate","cfd3d7",{"name":2932,"color":2933},3109,"SelectMenu search not working inside modal","2025-02-18T10:55:44Z","https://github.com/nuxt/ui/issues/3109",0.72928,["Reactive",2978],{},["Set"],["ShallowReactive",2981],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f9hMEZtTyUlnYPZNhvlqWKdhCwIgJM30n-QPgbV_a0vo":-1},"/nuxt/ui/2695"]