\n\u003C/template>\n```\n\nI think created items should emit `change` so we can validate them properly.\n\nAdditionally, because of https://github.com/nuxt/ui/issues/3736,the field always starts in an error state when a new item is created in certain conditions (regardless of whether the item meets the schema's requirements or not).\n\n------\n\nCurrent workaround is to run the validation manaully on a field after mutating the model:\n\n```ts\nasync function onCreate(item: string) {\n selected.value = item\n\n await formRef.value?.validate({ name: 'fieldName' })\n}\n```",[2852,2855],{"name":2853,"color":2854},"enhancement","a2eeef",{"name":2856,"color":2857},"v3","49DCB8",4139,"nuxt","ui","open","USelectMenu should emit 'change' after creating an item","2025-05-13T09:15:02Z","https://github.com/nuxt/ui/issues/4139",0.7599609,{"description":2867,"labels":2868,"number":2876,"owner":2859,"repository":2860,"state":2861,"title":2877,"updated_at":2878,"url":2879,"score":2880},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v22.13.1\n- Nuxt Version: 3.17.4\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: pnpm@10.6.3\n- Builder: -\n- User Config: telemetry, ssr, future, compatibilityDate, modules, hooks, nitro, css, routeRules, devtools, experimental, typescript, imports\n- Runtime Modules: @nuxt/ui-pro@3.1.3, @vueuse/nuxt@13.3.0, @pinia/nuxt@0.11.0, @pinia/colada-nuxt@0.2.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.1.3\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/suspicious-water-smppjv\n\n### Description\n\nThe docs note that you can access exposed variables from `UForm`. I've found that the following fields are not reactive:\n- dirty \n- dirtyFields\n- blurredFields\n- touchedFields\n\n### Additional context\n\nI see in the [source](https://github.com/nuxt/ui/blob/v3/src/runtime/components/Form.vue) that they're not defined with `ref` or `reactive`.\n\nAdditionally, the `dirty` computed that gets exposed would never get updated since `dirtyFields` is not reactive.\n\n### Logs\n\n```shell-script\n\n```",[2869,2872,2873],{"name":2870,"color":2871},"bug","d73a4a",{"name":2856,"color":2857},{"name":2874,"color":2875},"triage","ffffff",4238,"Form exposed dirty, dirtyFields, blurredFields, and touchedFields are not reactive","2025-05-28T03:58:59Z","https://github.com/nuxt/ui/issues/4238",0.76058745,{"description":2882,"labels":2883,"number":2887,"owner":2859,"repository":2860,"state":2861,"title":2888,"updated_at":2889,"url":2890,"score":2891},"### Description\n\n### Feature Request: Add `variant` and `status-position` props to `UProgress` component\n\n#### Description\nI’m a junior developer, and I’ve been working on enhancing the flexibility of the `Progress` component by adding two new props: `variant` and `status-position`. These props allow for better customization, especially when using the `Progress` component in different design contexts.\n\n- **`variant`**: This prop allows you to choose between two styles for the progress bar: `linear` and `circular`. The `circular` variant provides a circular progress bar instead of the default linear style.\n \n- **`status-position`**: This prop controls the position of the progress status (the percentage or label) relative to the progress bar. The possible values are:\n - `inside`: The status is displayed inside the circle (for the `circular` variant).\n - `outside`: The status is displayed outside the circle.\n\n#### Motivation\nThis update would help in using the `Progress` component more flexibly across different layouts, providing options for both linear and circular progress indicators with customizable label placements.\n\n#### What I've Done\nI’m still a junior developer, so the implementation is not perfect, but a good portion of the work is done. I’ve added the `variant` and `status-position` props to the `Progress` component. I’d love to know if this is something you’d like to integrate into the main repository and whether I can open a pull request for it.\n\n#### Additional Notes\n- The `variant` prop accepts values `linear` or `circular`.\n- The `status-position` prop accepts values `inside` or `outside`.\n \nWould love to hear your thoughts on this approach!\n\n\n### Additional context\n\n[Reka UI : Progress Circular](https://reka-ui.com/examples/progress-circular)",[2884,2885,2886],{"name":2853,"color":2854},{"name":2856,"color":2857},{"name":2874,"color":2875},3728,"[UProgress]: Add `variant` and `status-position` props","2025-03-29T14:31:22Z","https://github.com/nuxt/ui/issues/3728",0.7871384,{"description":2893,"labels":2894,"number":2898,"owner":2859,"repository":2860,"state":2861,"title":2899,"updated_at":2900,"url":2901,"score":2902},"### Description\n\nBased on https://ui.nuxt.com/components/form#error-event there is a way to attach things \"on form error\", like scroll the an element into view.\n\nThis does not help on back-end logic escalating a validation error or something some other logic coming from an external source.\n\nI tried\n\n- throwing an exception within submit, did not trigger the error handler\n- add errors through form refs `setErrors()`, then follow up with a `validate()` but that did nothing as well.\n\nIt would be nice to have a way to trigger the `@error` handler within the `@submit` handler, something in the spirit of:\n\n```js\nasync function onSubmit(event: FormSubmitEvent\u003C...>) {\n try { await api.doLogin() }\n catch (e) { event.fail() }\n}\n```\n\nNot sure this would be a good pattern though. Maybe if an exception is thrown within the submit handler, it could trigger the error handler as well?\n\n### Additional context\n\n_No response_",[2895,2896,2897],{"name":2853,"color":2854},{"name":2856,"color":2857},{"name":2874,"color":2875},4124,"UForm: Retrigger error handler on backend errors","2025-05-11T15:33:37Z","https://github.com/nuxt/ui/issues/4124",0.78995174,{"description":2904,"labels":2905,"number":2908,"owner":2859,"repository":2860,"state":2861,"title":2909,"updated_at":2910,"url":2911,"score":2912},"### Description\n\nI wanted to do something like the inline field label shown in the component examples in the docs, but couldn't find a suitable builtin. I think it's a nice halfway between MD's label-in-the-field strategy and while I could abuse the `leading` slot of the input, I think it makes more sense to be generic across input types. \n\n\n\nI did end up copy/pasting the source but it would be cool if the FormField (or something) had an `inline` variant that did this.\n\nFor reference:\nhttps://github.com/nuxt/ui/blob/50d68a636cc8b260dd3b8cf8afecb3b564b9d75d/docs/app/components/content/ComponentExample.vue#L162-L167\n\nThanks for your consideration 😄 \n\n### Additional context\n\n_No response_",[2906,2907],{"name":2853,"color":2854},{"name":2856,"color":2857},3543,"Inline Form Field Label","2025-03-14T11:13:49Z","https://github.com/nuxt/ui/issues/3543",0.789962,{"description":2914,"labels":2915,"number":2920,"owner":2859,"repository":2860,"state":2921,"title":2922,"updated_at":2923,"url":2924,"score":2925},"### 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```",[2916,2919],{"name":2917,"color":2918},"question","d876e3",{"name":2856,"color":2857},3294,"closed","UCheckbox fieldform support","2025-02-12T19:23:36Z","https://github.com/nuxt/ui/issues/3294",0.74507046,{"description":2927,"labels":2928,"number":2931,"owner":2859,"repository":2860,"state":2921,"title":2932,"updated_at":2933,"url":2934,"score":2935},"### Description\n\nUsing [NavigationMenu](https://ui3.nuxt.dev/components/navigation-menu) parent items are currently always collapsible. The following is not possible:\n\n\u003Cimg width=\"252\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/21c6d595-d24d-47c8-bdb5-064a7582f5ec\" />\n\nIt would be an amazing to have a new prop `collapsible: boolean`. If set to true the parent is not clickable and the children are always visible.\n\n### Additional context\n\n_No response_",[2929,2930],{"name":2853,"color":2854},{"name":2856,"color":2857},2993,"NavigationMenu with non-collapsible parents","2025-02-15T17:01:06Z","https://github.com/nuxt/ui/issues/2993",0.75940347,{"description":2937,"labels":2938,"number":2943,"owner":2859,"repository":2860,"state":2921,"title":2944,"updated_at":2945,"url":2946,"score":2947},"### Environment\n\nJust reporting an issue on the nuxt docs site. \n\n### Version\n\nhttps://ui.nuxt.com/components/button\n\n### Reproduction\n\nGo on to the nuxt website, this section in particular: \n\nhttps://ui.nuxt.com/components/button#icon\n \nand click 'trailing'. this should reproduce the issue. \n\n\n### Description\n\nWhen on the live docs site, on the button page, clicking 'trailing' docs this happens: \n\n\n\nThe page is: \n\nhttps://ui.nuxt.com/components/button#icon\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2939,2940],{"name":2870,"color":2871},{"name":2941,"color":2942},"documentation","0075ca",2425,"Bug on live docs site","2024-10-21T10:20:07Z","https://github.com/nuxt/ui/issues/2425",0.7618403,{"description":2949,"labels":2950,"number":2952,"owner":2859,"repository":2860,"state":2921,"title":2953,"updated_at":2954,"url":2955,"score":2956},"### For what version of Nuxt UI are you asking this question?\n\nv2.x\n\n### Description\n\nIs that normal to tooltip doesn’t work on mobile? I’m using safari on iOS iPhone and the tooltip doesn’t work\n\nhttps://ui.nuxt.com/components/tooltip",[2951],{"name":2917,"color":2918},2419,"Bug on tooltip?","2024-12-03T11:02:22Z","https://github.com/nuxt/ui/issues/2419",0.7788378,{"description":2958,"labels":2959,"number":2962,"owner":2859,"repository":2860,"state":2921,"title":2963,"updated_at":2964,"url":2965,"score":2966},"### Description\n\nThe aria-invalid property is missing too.",[2960,2961],{"name":2917,"color":2918},{"name":2856,"color":2857},3241,"Why there is no invalid prop on form elements?","2025-02-05T06:30:21Z","https://github.com/nuxt/ui/issues/3241",0.78251326,["Reactive",2968],{},["Set"],["ShallowReactive",2971],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fp6JJDy2vWgBsZ_F66eiBdABTXFxRMExuQAP9tBCgNwM":-1},"/nuxt/ui/1815"]