\n \u003C/div>\n\u003C/template>\n```\n\n### Logs\n\n```shell-script\n\n```",[3207,3208],{"name":3135,"color":3136},{"name":3158,"color":3159},2755,"Veritcal NavigationMenu - `defaultOpen` doesn't work","2024-11-26T10:29:27Z","https://github.com/nuxt/ui/issues/2755",0.62614524,{"description":3215,"labels":3216,"number":3219,"owner":3144,"repository":3145,"state":3146,"title":3220,"updated_at":3221,"url":3222,"score":3223},"### Description\n\nI want to configure my Nuxt UI v3 project only to use black and white colors with the neutral palette from Tailwind, similar to the one found in shadcn. I understand Nuxt UI supports Tailwind CSS theming, but I’m unsure of the best/recommended way to override all component colors globally",[3217,3218],{"name":3155,"color":3156},{"name":3158,"color":3159},3200,"How to create a black & white only theme in Nuxt UI v3","2025-02-09T12:59:38Z","https://github.com/nuxt/ui/issues/3200",0.6373719,{"description":3225,"labels":3226,"number":3231,"owner":3144,"repository":3145,"state":3146,"title":3232,"updated_at":3233,"url":3234,"score":3235},"### For what version of Nuxt UI are you suggesting this?\n\nv3-alpha\n\n### Description\n\nIn v2 (https://ui.nuxt.com/components/modal#prevent-close):\n> Use the prevent-close prop to disable the outside click alongside the esc keyboard shortcut. A close-prevented event will be emitted when the user tries to close the modal.\n\nIn v3 (https://ui3.nuxt.dev/components/modal#prevent-close):\n> Use the prevent-close prop to prevent the Modal from being closed when clicking outside of it.\n\nI'd like to have similar behavior in v3 as in v2, i.e. being able to prevent closing the modal (by any means) but being able to capture and handle this event on my own.\n\n### Additional context\n\n_No response_",[3227,3230],{"name":3228,"color":3229},"enhancement","a2eeef",{"name":3158,"color":3159},2501,"[Modal] prevent-close differs between v2 and v3","2024-11-10T09:20:14Z","https://github.com/nuxt/ui/issues/2501",0.6389544,{"description":3237,"labels":3238,"number":3241,"owner":3144,"repository":3145,"state":3146,"title":3242,"updated_at":3243,"url":3244,"score":3245},"### 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_",[3239,3240],{"name":3228,"color":3229},{"name":3158,"color":3159},2302,"Form validation properties","2025-01-24T18:10:45Z","https://github.com/nuxt/ui/issues/2302",0.6405513,["Reactive",3247],{},["Set"],["ShallowReactive",3250],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fdWBQ98h07-8dJBjbgvmf8tFeibEp4yWNJxQxb28MpFk":-1},"/nuxt/nuxt.com/1386"]