\n \u003Ctemplate #content>\n \u003CUDropdownMenu\n :items=\"items\"\n >\n \u003CUButton label=\"Open Drop down\"/>\n \u003C/UDropdownMenu>\n \u003C/template>\n \u003C/UDrawer>\n\u003C/template>\n```\n\n### Logs\n\n```shell-script\nUncaught InternalError: too much recursion\n NuxtJS 5\n focus\n handleFocusOut\n ct\n f\n focus\n```",[3108,3109,3110],{"name":3074,"color":3099},{"name":3041,"color":3042},{"name":3111,"color":3112},"reka-ui","56d799",3357,"Cant put dropdown inside drawer","2025-04-08T19:49:57Z","https://github.com/nuxt/ui/issues/3357",0.6663519,{"description":3119,"labels":3120,"number":3125,"owner":3019,"repository":3044,"state":3057,"title":3126,"updated_at":3127,"url":3128,"score":3129},"### Description\n\nFor custom validation or for using the Form with Zod, etc. it would be great to have the common form field properties `touched` and `dirty` exposed.\n\n- `Touched` (opposite of `untouched`): A field is considered touched when a user has focused it OR changed it's value\n- `Dirty` (opposite of `pristine`): A field is considered dirty, if the value has changed (AND is different from its initial value). The second part is depending on the definition.\n\nYou can currently work around most of these by using a computed on the exposed `errors` ref and the state reactive, but for custom validation having these values natively exposed from the API would be very helpful.\n\n### Additional context\n\n_No response_",[3121,3124],{"name":3122,"color":3123},"enhancement","a2eeef",{"name":3041,"color":3042},2302,"Form validation properties","2025-01-24T18:10:45Z","https://github.com/nuxt/ui/issues/2302",0.6679164,["Reactive",3131],{},["Set"],["ShallowReactive",3134],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fuuAutq3qbYNxWxZzjyuOo8Jiks63smjN8_2X7S7cNMU":-1},"/nuxt/ui/2622"]