isn't rendering","2025-01-08T09:24:13Z","https://github.com/nuxt/ui/issues/3044",0.67034477,{"description":2963,"labels":2964,"number":2965,"owner":2911,"repository":2922,"state":2947,"title":2966,"updated_at":2967,"url":2968,"score":2969},"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.6706623,{"description":2971,"labels":2972,"number":2978,"owner":2911,"repository":2912,"state":2947,"title":2979,"updated_at":2980,"url":2981,"score":2982},"### Description\n\nI’ve been using USlideover from NuxtUI (v3), and I noticed that there’s no event triggered when clicking on the overlay (outside of the slideover). This makes it tricky to detect when a user dismisses it by clicking outside, rather than using the close button.\n\nIt would be super helpful if USlideover emitted an event whenever it’s closed—whether that’s via the close button or the overlay. That way, we could easily handle any necessary logic when the slideover is dismissed.\n\nIf exposing a close event isn’t feasible, maybe the overlay could be made accessible as a slot? That way, we could wrap it in our own template and attach a @click event directly. This would give us more flexibility in handling interactions.\n\nI took a look at the source code, and it seems like these interactions are already handled internally, but they aren’t exposed as events:\n🔗 [Slideover.vue](https://github.com/nuxt/ui/blob/v3/src/runtime/components/Slideover.vue)\n\nWould be awesome to see this in a future update.\n\n### Additional context\n\n_No response_",[2973,2976,2977],{"name":2974,"color":2975},"enhancement","a2eeef",{"name":2908,"color":2909},{"name":2935,"color":2936},3225,"Expose close event for USlideover (Overlay & Button)","2025-03-28T17:34:38Z","https://github.com/nuxt/ui/issues/3225",0.6762245,{"description":2984,"labels":2985,"number":2986,"owner":2911,"repository":2922,"state":2947,"title":2987,"updated_at":2988,"url":2989,"score":2990},"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.68117493,{"description":2992,"labels":2993,"number":2996,"owner":2911,"repository":2912,"state":2947,"title":2997,"updated_at":2998,"url":2999,"score":3000},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v22.11.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.15.0\n- Nitro Version: -\n- Package Manager: pnpm@9.14.2\n- Builder: -\n- User Config: default\n- Runtime Modules: ../src/module, @nuxt/ui@3.0.0-alpha.9\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n^3.0.0-alpha.9\n\n### Reproduction\n\nNormal Nuxt app setup as mentioned here https://ui3.nuxt.dev/getting-started/installation/nuxt\n- Use latest Nuxt app. \n- Add @tailwindcss 4 with vite and install this @nuxt/ui module and add it to Nuxt app. \n- Add @nuxt/ui import to tailwind css file\n\n### Description\n\n- Components such as UButton displays nicely\n- Components such as Accordion or Drawer fails. \n\nHere's a sample code used in `pages/index.vue` file\n\n```html\n\u003CUButton :ui=\"{ base: 'bg-primary-500' }\" class=\"inline-block\">UButton\u003C/UButton>\n\n \u003CUButton label=\"Show toast\" color=\"secondary\" variant=\"solid\" @click=\"showToast\" />\n\n \u003C!-- \u003CUAccordion :items=\"items\" /> -->\n\n \u003CUDrawer id=\"drawer\">\n \u003CUButton label=\"Open\" color=\"surface\" variant=\"solid\" />\n \u003Ctemplate #content>\n \u003CBaseUiPlaceholder class=\"h-48 m-4\" />\n \u003C/template>\n \u003C/UDrawer>\n```\n\nIf we use Accordion or Drawer (as mentioned in above code), we get 500 Error and app crashes. \n\n\n\nIf we comment out the Accordion and Drawer, no error comes, and app works nicely. \n\n\n\nSee: No error if we don't use the error-causing components. \n\n\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2994,2995],{"name":2931,"color":2932},{"name":2908,"color":2909},2769,"[v3] Error `$setup.useId is not a function` in Accordion, Drawer, etc.","2024-11-26T13:44:15Z","https://github.com/nuxt/ui/issues/2769",0.68263155,{"description":3002,"labels":3003,"number":3004,"owner":2911,"repository":2922,"state":2947,"title":3005,"updated_at":3006,"url":3007,"score":3008},"There seems to be a bug with the integrations active class in header\r\n\r\nhttps://github.com/nuxt/nuxt.com/assets/38922203/d50705a7-ae7f-4317-ac3c-867d41ac76ac\r\n\r\n",[],1432,"Integration active class ","2023-11-22T14:26:00Z","https://github.com/nuxt/nuxt.com/issues/1432",0.682678,["Reactive",3010],{},["Set"],["ShallowReactive",3013],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fIC5ldUZGgiiSG2Dzyx_9CUp_AbC1lVF5ly4yh4Q5W8Q":-1},"/nuxt/ui/2907"]