\n \u003C/template>\n\u003C/UModal>\n```\n\n\n### Description\n\nselect menu's search input always autofocus inside modal, even when the autofocus is set to false.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3018,3021,3024],{"name":3019,"color":3020},"bug","d73a4a",{"name":3022,"color":3023},"v3","49DCB8",{"name":3025,"color":3026},"triage","ffffff",3933,"nuxt","ui","open","SelectMenu's autofocus doesn't work inside Modal","2025-04-19T06:22:26Z","https://github.com/nuxt/ui/issues/3933",0.6625081,{"description":3036,"labels":3037,"number":3043,"owner":3028,"repository":3029,"state":3030,"title":3044,"updated_at":3045,"url":3046,"score":3047},"### Description\n\nWould be nice to add the possibility to set the position of the loading icon in the `UButton`. Now it replaces the leading icon, but when the trailing icon is used this leads to a behavior that in my opinion is undesidered in the majority of cases. \nThe idea would be a prop like that:\n```ts\nloading-position: 'leading' | 'trailing' | 'auto'\n```\nwhere `auto` should place the loader where the button icon is placed, leading otherwise.\n\n### Additional context\n\n_No response_",[3038,3041,3042],{"name":3039,"color":3040},"enhancement","a2eeef",{"name":3022,"color":3023},{"name":3025,"color":3026},3419,"Add `loading-position` to `UButton`","2025-03-02T12:16:32Z","https://github.com/nuxt/ui/issues/3419",0.69293135,{"description":3049,"labels":3050,"number":3053,"owner":3028,"repository":3054,"state":3055,"title":3056,"updated_at":3057,"url":3058,"score":3059},"- [x] `/modules`\n- [x] `/community/repositories`\n- [x] `/community/partners`\n- [x] `/resources/showcases`",[3051],{"name":3039,"color":3052},"1ad6ff",597,"nuxt.com","closed","[Responsive] Display aside filters on list pages","2023-02-15T12:32:35Z","https://github.com/nuxt/nuxt.com/issues/597",0.6162009,{"description":3061,"labels":3062,"number":3066,"owner":3028,"repository":3029,"state":3055,"title":3067,"updated_at":3068,"url":3069,"score":3070},"### Description\n\nHi, using the UTable with Expanded feature is it possible to apply a style to the Expand column ??? I can see how to do this for columns I add but not the expanded column.\r\nAlso is it possible to change the default so the expanded is open by default? Or to change this in the script section?\r\n\r\nThanks I was unable to find answers in the docs.",[3063],{"name":3064,"color":3065},"question","d876e3",2244,"UTable Expandable questions?","2024-11-05T14:52:12Z","https://github.com/nuxt/ui/issues/2244",0.62037295,{"description":3072,"labels":3073,"number":3076,"owner":3028,"repository":3029,"state":3055,"title":3077,"updated_at":3078,"url":3079,"score":3080},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: 3.16.0\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.7\n- Package Manager: pnpm@10.6.3\n- Builder: -\n- User Config: compatibilityDate, devtools, future, experimental, modules, vite, css, typescript\n- Runtime Modules: @nuxt/eslint@1.2.0, @nuxt/test-utils@3.17.2, @nuxt/icon@1.11.0, @nuxt/ui@3.0.0\n- Build Modules: -\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/input-menu\n\n### Description\n\nThe InputMenu component only shows filtered items when opening it with a selected item. This is confusing, and differs from expected behavior. In its current state, the InputMenu would only be usable, if the user deletes the text in the field, which is not clear nor expected.\n\nExpected behavior: If one opens the select menu by clicking on the button, it shows all available values, with the currently selected value highlighted. Only when changing the text of the input field, it filters for the value entered.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3074,3075],{"name":3019,"color":3020},{"name":3022,"color":3023},3620,"InputMenu shows only selected item when opening","2025-03-27T15:27:51Z","https://github.com/nuxt/ui/issues/3620",0.63393426,{"description":3082,"labels":3083,"number":3085,"owner":3028,"repository":3029,"state":3055,"title":3086,"updated_at":3087,"url":3088,"score":3089},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v22.11.0\n- Nuxt Version: 3.14.0\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.2\n- Package Manager: npm@10.9.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/eslint@0.5.7, @nuxt/fonts@0.7.2, @nuxt/ui@2.19.0, @vueuse/nuxt@10.11.1, @pinia/nuxt@0.5.5, @pinia-plugin-persistedstate/nuxt@1.2.1, @nuxtjs/i18n@8.5.6, @nuxtjs/tailwindcss@6.12.2, @vite-pwa/nuxt@0.10.6\n- Build Modules: -\n------------------------------\n\n### Version\n\nv.2.19.0\n\n### Reproduction\n\nUpgrade nuxt/ui to latest 2.19.0 version\n\n### Description\n\nSelectMenu component is broken from what it seems to be a mistake in the a merge conflict.\n\n\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3084],{"name":3019,"color":3020},2534,"Critical bug in SelectMenu.vue","2024-11-05T16:58:09Z","https://github.com/nuxt/ui/issues/2534",0.645886,{"description":3091,"labels":3092,"number":3095,"owner":3028,"repository":3029,"state":3055,"title":3096,"updated_at":3097,"url":3098,"score":3099},"### Environment\n\nNuxt 3.15.4\nNuxt UI https://pkg.pr.new/@nuxt/ui@e7e7585\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.15.4\n\n### Reproduction\n\n-\n\n### Description\n\nJust noticed the following components work as expected in a fieldForm\n\n```\n \u003CUFormField\n v-if=\"isVisible\"\n :name=\"fieldName\"\n :label=\"field['#title']\"\n :required=\"!!field['#required']\"\n >\n \u003Ctemplate\n v-if=\"descriptionContent && field['#type'] !== 'checkbox'\"\n #description\n >\n \u003Cspan v-html=\"cleanHTML(descriptionContent)\" />\n \u003C/template>\n\n \u003Ccomponent\n v-if=\"resolvedComponent\"\n :is=\"resolvedComponent\"\n :field=\"field\"\n :fieldName=\"fieldName\"\n :state=\"state\"\n />\n\n \u003Ctemplate v-if=\"helpContent\" #help>\n \u003Cspan v-html=\"cleanHTML(helpContent)\" />\n \u003C/template>\n \u003C/UFormField>\n```\n\n ```\n \u003CURadioGroup\n v-model=\"state[fieldName]\"\n :items=\"transformOptions(field['#options'] || {})\"\n orientation=\"horizontal\"\n class=\"w-full\"\n />\n```\n\n```\n \u003CUSelect\n v-model=\"state[fieldName]\"\n placeholder=\"Select\"\n :items=\"transformOptions(field['#options'] || {})\"\n class=\"w-full\"\n />\n\n```\nHowever when using a UCheckbox label and description have to be set here\n\n```\n \u003CUCheckbox\n v-model=\"checkboxValue\"\n :label=\"field['#title']\"\n :description=\"field['#description']\"\n class=\"w-full\"\n @update:model-value=\"props.state[fieldName] = $event\"\n />\n```\n\nSeems like this is a bug or maybe this is by design?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3093,3094],{"name":3064,"color":3065},{"name":3022,"color":3023},3294,"UCheckbox fieldform support","2025-02-12T19:23:36Z","https://github.com/nuxt/ui/issues/3294",0.6531999,{"description":3101,"labels":3102,"number":3105,"owner":3028,"repository":3029,"state":3055,"title":3106,"updated_at":3107,"url":3108,"score":3109},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.12.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.22.2\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@8.14.1\n- Builder: -\n- User Config: devtools, future, compatibilityDate, typescript, modules, components, ui, css, vite, formkit\n- Runtime Modules: @nuxt/icon@1.10.3, @formkit/nuxt@1.6.9, @nuxt/image@1.9.0, @vueuse/nuxt@12.5.0, @nuxt/ui@3.0.0-alpha.13\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.0-alpha.13\n\n### Reproduction\n\n--\n\n### Description\n\nAccording to the documentation, the Button component accepts props `active` which theoretically should force an `active` state for the button - unfortunately adding this does not change anything. \nIn addition, there is a lack of styles and support for the active button (as is the case with links) \n\nWhat I would like to achieve: \nI want the navigation menu to consist of links that visually look like buttons, in addition, I would like the button (if it is under the address to which it leads) to be active (visually distinguished from the other buttons)\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3103,3104],{"name":3019,"color":3020},{"name":3022,"color":3023},3417,"No option to set button as active, no styles for active buttons","2025-03-08T21:49:08Z","https://github.com/nuxt/ui/issues/3417",0.65624684,{"description":3111,"labels":3112,"number":3115,"owner":3028,"repository":3029,"state":3055,"title":3116,"updated_at":3117,"url":3118,"score":3119},"### Description\n\nHi,\n\nI just tried upgrading to `v3` but I noticed that the `Meter` component is unfortunately missing in this version and the migration guide also doesn't mention anything regarding that component which currently prevents me from upgrading to v3 . [This issue](https://github.com/nuxt/ui/issues/1841) mentions that the component was still pending migration at some point in the beginning of 2024 besides some other components.\n\nIs the meter component still expected to arrive in v3 sometime soon? It would be quite unfortunate if this handy component would be stripped out of NuxtUI.\n",[3113,3114],{"name":3064,"color":3065},{"name":3022,"color":3023},3808,"Meter component missing in v3","2025-04-08T17:16:45Z","https://github.com/nuxt/ui/issues/3808",0.65849143,{"description":3121,"labels":3122,"number":3124,"owner":3028,"repository":3125,"state":3055,"title":3126,"updated_at":3127,"url":3128,"score":3129},"Thought this issue was related to my project, but I was able to reproduce it, sounds weird but this font won't work on a production build - https://fonts.google.com/specimen/DM+Serif+Display\r\n\r\nI am using the font by mentioning it in my tailwind config \r\n\r\n```ts\r\nimport type { Config } from \"tailwindcss\";\r\n\r\nexport default \u003CPartial\u003CConfig>>{\r\n theme: {\r\n fontFamily: {\r\n sans: [\r\n \"DM Sans\",\r\n \"Avenir Next\",\r\n \"Roboto\",\r\n \"-apple-system\",\r\n \"BlinkMacSystemFont\",\r\n '\"Segoe UI\"',\r\n \"Ubuntu\",\r\n '\"Helvetica Neue\"',\r\n \"Arial\",\r\n '\"Noto Sans\"',\r\n \"sans-serif\",\r\n '\"Apple Color Emoji\"',\r\n '\"Segoe UI Emoji\"',\r\n '\"Segoe UI Symbol\"',\r\n '\"Noto Color Emoji\"',\r\n ],\r\n mono: [\r\n \"Cascadia Code\",\r\n \"ui-monospace\",\r\n \"SFMono-Regular\",\r\n \"Menlo\",\r\n \"Monaco\",\r\n \"Consolas\",\r\n \"Liberation Mono\",\r\n \"Courier New\",\r\n \"monospace\",\r\n ],\r\n display: [\"DM Serif Display\", \"Inter\", \"sans-serif\"],\r\n },\r\n },\r\n plugins: [require(\"@tailwindcss/typography\")],\r\n};\r\n```\r\n\r\nThe first font `DM Sans` is loads correctly, but the display font wont, throws a 404 in production.\r\n\r\nHere's a reproduction - https://github.com/fayazara/nuxt-font-repro\r\n\r\nDev environment screenshot \r\n\r\n\r\n\r\nProduction screenshot\r\n",[3123],{"name":3019,"color":3020},122,"fonts","This font won't work on production: DM Serif Display","2024-05-03T08:11:09Z","https://github.com/nuxt/fonts/issues/122",0.666101,["Reactive",3131],{},["Set"],["ShallowReactive",3134],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fq2f0Ref1sK4VSmFT3M3hencOp2ym3HviRcqfJ-0Qfqw":-1},"/nuxt/ui/3595"]