\n \u003C/div>\n\u003C/template>\n```\n\n### Logs\n\n```shell-script\n\n```",[3166,3169],{"name":3167,"color":3168},"bug","d73a4a",{"name":3154,"color":3155},2755,"Veritcal NavigationMenu - `defaultOpen` doesn't work","2024-11-26T10:29:27Z","https://github.com/nuxt/ui/issues/2755",0.6627287,{"description":3176,"labels":3177,"number":3182,"owner":3140,"repository":3157,"state":3158,"title":3183,"updated_at":3184,"url":3185,"score":3186},"### 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_",[3178,3181],{"name":3179,"color":3180},"enhancement","a2eeef",{"name":3154,"color":3155},2501,"[Modal] prevent-close differs between v2 and v3","2024-11-10T09:20:14Z","https://github.com/nuxt/ui/issues/2501",0.6635567,{"description":3188,"labels":3189,"number":3191,"owner":3140,"repository":3157,"state":3158,"title":3192,"updated_at":3193,"url":3194,"score":3195},"### For what version of Nuxt UI are you suggesting this?\n\nv2.x\n\n### Description\n\nThe config of the divider component allows to define types:\n\n```\ntype: {\n solid: 'border-solid',\n dotted: 'border-dotted',\n dashed: 'border-dashed',\n},\n```\n\nHowever, the solid type is set by default and can only be changed per Divider component, not globally via config. It would be great to be able to set a custom default type like so:\n\n```\ndefault: {\n border: {\n type: 'dotted',\n },\n},\n```\n\n### Additional context\n\n_No response_",[3190],{"name":3179,"color":3180},2398,"Define default type for Divider","2024-10-19T12:19:23Z","https://github.com/nuxt/ui/issues/2398",0.66453403,{"description":3197,"labels":3198,"number":3201,"owner":3140,"repository":3157,"state":3158,"title":3202,"updated_at":3203,"url":3204,"score":3205},"### Description\n\nHello, I just wanted to overwrite shadow-sm with another shadow in the card root slot.\nBut I failed to do so. I tried the :ui way and the app.config.ts way but in both cases the new class \"shadow-card\" ended up BEHIND \"shadow-sm\".\n\n```\n card: {\n slots: {\n root: \"shadow-card\",\n },\n },\n```\n\nSo shadow-card always gets overwritten by shadow-sm cause the code always ends up like this:\n```\n\u003Cdiv class=\"bg-[var(--ui-bg)] ring ring-[var(--ui-border)] divide-y divide-[var(--ui-border)] rounded-[calc(var(--ui-radius)*2)] shadow-sm shadow-card\">\n```\n\nso how can I overwrite shadow-sm here?",[3199,3200],{"name":3151,"color":3152},{"name":3154,"color":3155},2936,"Overwrite css classes of slots","2025-01-08T16:26:22Z","https://github.com/nuxt/ui/issues/2936",0.66887957,{"description":3207,"labels":3208,"number":3209,"owner":3140,"repository":3141,"state":3158,"title":3210,"updated_at":3211,"url":3212,"score":3213},"On the 'Enterprise Jobs' page, location badges were closely together on mobile screens. I removed the `mr-3` class from the badge element and placed the badges inside a parent `\u003Cdiv>` with the classes` flex`, `flex-wrap`, and `gap-3` Now it won't stick together and will look good on mobile devices.\r\n\r\n| **BEFORE** | **AFTER** | \r\n|-------- | ------ | \r\n|  |  |\r\n\r\n\r\n\r\n\n```[tasklist]\n### Tasks\n```\n",[],1403,"Spacing issue with Location badges on 'Enterprise Jobs' page for mobile screens","2024-09-19T19:38:43Z","https://github.com/nuxt/nuxt.com/issues/1403",0.6736921,{"description":3215,"labels":3216,"number":3217,"owner":3140,"repository":3141,"state":3158,"title":3218,"updated_at":3219,"url":3220,"score":3221},"After using `pnpm update` to upgrade vue to 3.4.3, the console throws a lot of `Hydration mismatch`. If I am using vue 3.3.13, no `Hydration mismatch` warnings will be thrown.\r\n\r\n\u003Cimg width=\"1402\" alt=\"SCR-20240103-qagg\" src=\"https://github.com/nuxt/nuxt.com/assets/133459587/188ac1c4-e19a-4570-a5d0-4863c92a7bda\">\r\n",[],1467,"About vue@3.4.3 causing hydration mismatch","2024-05-03T00:34:36Z","https://github.com/nuxt/nuxt.com/issues/1467",0.6739373,{"description":3223,"labels":3224,"number":3230,"owner":3140,"repository":3157,"state":3158,"title":3231,"updated_at":3232,"url":3233,"score":3234},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.18.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.16.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.12.3\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/image@1.8.1, @nuxt/content@2.13.4, @nuxthq/studio@1.1.2, @nuxt/ui-pro@3.0.0-alpha.10, @nuxtjs/plausible@1.2.0, @nuxtjs/seo@2.0.2, @vueuse/nuxt@12.0.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0.alpha10\n\n### Reproduction\n\nhttps://ui3.nuxt.dev/components/button#loading (example with `loading-auto`)\n\n### Description\n\nWhen using a `UIButton` component with an `@click` event, the cursor does not change to `cursor-pointer`, which may confuse users about the button's clickability.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3225,3226,3229],{"name":3167,"color":3168},{"name":3227,"color":3228},"duplicate","cfd3d7",{"name":3154,"color":3155},2940,"`cursor-pointer` is missing on `UButton` with an `@click` event","2025-04-02T09:37:12Z","https://github.com/nuxt/ui/issues/2940",0.67754596,{"description":3236,"labels":3237,"number":3240,"owner":3140,"repository":3157,"state":3158,"title":3241,"updated_at":3242,"url":3243,"score":3244},"### Description\n\ni noticed that NUXT UI / NUXT UI PRO were refactored to use tailwind's new version 3 stuff + radix...\n\ni just went to the tailwind docs today and it looks like they just skipped right past their new version 3 and went to version 4...\n\nany ideas how this effects NUXT UI/PRO? \n\nMy undersanding is that version 3->4 means it was a semver breaking change?",[3238,3239],{"name":3151,"color":3152},{"name":3154,"color":3155},3167,"tailwind version 4..?","2025-01-24T10:17:32Z","https://github.com/nuxt/ui/issues/3167",0.6792719,["Reactive",3246],{},["Set"],["ShallowReactive",3249],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fjSK9WVoR8PWkSjNNLiW4ELv_-S7TpB0vMbazxj9k050":-1},"/nuxt/ui/2301"]