\n\n## npx nuxi dev\n\n\u003Cimg width=\"1717\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/c362da21-f5f9-4c7d-a91c-f60bf6de9c0b\" />\n\n### Additional context\n\nThe classes are recognized in the .playground it seems. If I redefine the header, footer and layout in the playground they are displayed correctly. \n\n[header/footer/layout added to .playground](https://github.com/deetz99/ui3-layer-test/tree/test)\n\nIt seems that the styles aren't applied to the components that come from the layer.\n\n### Logs\n\n```shell-script\n\n```",[2910,2911,2912],{"name":2883,"color":2884},{"name":2869,"color":2870},{"name":2900,"color":2901},3544,"Tailwind classes missing when using layers","2025-03-14T19:00:15Z","https://github.com/nuxt/ui/issues/3544",0.74687797,{"description":2919,"labels":2920,"number":2923,"owner":2872,"repository":2873,"state":2887,"title":2924,"updated_at":2925,"url":2926,"score":2927},"### Environment\n\n- Operating System: Linux\n- Node Version: v18.18.2\n- Nuxt Version: 3.13.2\n- CLI Version: 3.14.0\n- Nitro Version: 2.9.7\n- Package Manager: bun@1.1.27\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Version\n\ne6143e8\n\n### Reproduction\n\nThis issue can be seen in the official demo at https://ui3.nuxt.dev/components/context-menu, so I don't think a reproduction is necessary.\n\n### Description\n\nWhen right clicking twice into the same \"block\", the browser context menu opens instead of the custom context menu. This also happens if multiple `\u003CUContextMenu>` blocks are used on the same page, when right clicking into one, and then directly into another one (without clicking anywhere else in between) opens the default browser context menu.\n\nv2 did not have the same behaviour, and this does not seem to happen in the [Radix Vue demo](https://www.radix-vue.com/components/context-menu).\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2921,2922],{"name":2883,"color":2884},{"name":2869,"color":2870},2399,"ContextMenu: Right clicking twice or at a different context menu causes browser context menu to show","2024-11-28T13:56:19Z","https://github.com/nuxt/ui/issues/2399",0.7563909,{"labels":2929,"number":2938,"owner":2872,"repository":2872,"state":2887,"title":2939,"updated_at":2940,"url":2941,"score":2942},[2930,2932,2935],{"name":2931,"color":2901},"stale",{"name":2933,"color":2934},"pending triage","E99695",{"name":2936,"color":2937},"2.x","d4c5f9",8023,"Dollar sign ($) in .env value converted to 'undefined' in $config","2023-01-22T15:36:07Z","https://github.com/nuxt/nuxt/issues/8023",0.7599964,{"description":2944,"labels":2945,"number":2948,"owner":2872,"repository":2873,"state":2887,"title":2949,"updated_at":2889,"url":2950,"score":2951},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v20.12.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@10.4.1\n- Builder: -\n- User Config: extends, modules, $production, devtools, app, css, site, runtimeConfig, sourcemap, future, experimental, compatibilityDate, nitro, eslint, linkChecker, sitemap\n- Runtime Modules: @nuxt/ui-pro@3.0.0-alpha.13, @nuxtjs/seo@2.1.1, @nuxt/content@3.1.1, @sentry/nuxt/module@8.55.0\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.13\n\n### Reproduction\n\nNo reproduction is needed. Prop.state is mutated.\n\n### Description\n\nThe current implementation of the Form component has two significant issues:\n\n\n1. **Direct Prop Mutation**: The component directly mutates its `state` prop, which violates Vue's fundamental rules about prop mutation. From Vue's documentation: [https://vuejs.org/guide/components/props.html#one-way-data-flow](https://vuejs.org/guide/components/props.html#one-way-data-flow)\n> \"All props form a one-way-down binding between the child property and the parent one: when the parent property updates, it will flow down to the child, but not the other way around. This prevents child components from accidentally mutating the parent's state, which can make your app's data flow harder to understand.\"\n\n2. **Breaks Immutable State Patterns**: The direct mutation approach is incompatible with modern state management patterns that rely on immutable state updates.\n\nThe problematic code is in the `_validate` function:\n```typescript\nif (opts.transform) {\n Object.assign(props.state, transformedState.value)\n}\n\n```\n\nhttps://github.com/nuxt/ui/blob/v3/src/runtime/components/Form.vue\n\nLine 182",[2946,2947],{"name":2883,"color":2884},{"name":2869,"color":2870},3354,"Form component violates Vue prop mutation rules and breaks immutable state patterns","https://github.com/nuxt/ui/issues/3354",0.76192117,{"description":2953,"labels":2954,"number":2959,"owner":2872,"repository":2873,"state":2887,"title":2960,"updated_at":2961,"url":2962,"score":2963},"### Environment\n\n```\nNuxt project info: 4:16:28 PM\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.14.0\n- Nuxt Version: 3.14.159\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@8.8.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@2.19.2, @nuxt/eslint@0.3.13, @nuxt/test-utils/module@3.14.4, @pinia/nuxt@0.5.5, @vueuse/nuxt@10.11.1, nuxt-shiki@0.3.0, nuxt-svgo@4.0.8\n- Build Modules: -\n------------------------------\n```\n\n### Version\n\nv2.19.2\n\n### Reproduction\n\nI don't know how to reproduce it unfortunately.\n\n### Description\n\nI often have a bunch of `[Icon] loading icon `heroicons:magnifying-glass` timed out after 500ms` on firefox\n\n\n\nit impacts the breadcrumb component\n\nbut also other `\u003CUIcon>` instances\n\nDo you have any idea about where those timeouts maybe coming from \n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2955,2956],{"name":2883,"color":2884},{"name":2957,"color":2958},"upstream","78bddb",2573,"Icon timeout despite having installed the @iconify-json/heroicons collection","2024-11-08T16:41:20Z","https://github.com/nuxt/ui/issues/2573",0.76276296,{"description":2965,"labels":2966,"number":2974,"owner":2872,"repository":2872,"state":2887,"title":2975,"updated_at":2976,"url":2977,"score":2978},"### Environment\r\n\r\nWorking directory: C:/dev/hotel-viewer 21:00:40\r\nNuxt project info: 21:00:40\r\n\r\n------------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v20.10.0\r\n- Nuxt Version: 3.9.3\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: yarn@1.22.21\r\n- Builder: -\r\n- User Config: devtools, modules, runtimeConfig, colorMode, ssr, app, googleFonts, ui, nitro\r\n- Runtime Modules: @nuxt/ui@2.12.3, @pinia/nuxt@0.5.1, @nuxtjs/google-fonts@3.1.3\r\n- Build Modules: -\r\n------------------------------\r\n\r\n👉 Report an issue: https://github.com/nuxt/nuxt/issues/new 21:00:40\r\n\r\n👉 Suggest an improvement: https://github.com/nuxt/nuxt/discussions/new\r\n\r\n👉 Read documentation: https://nuxt.com\r\n\r\n### Reproduction\r\n\r\n↓\r\n\r\n### Describe the bug\r\n\r\nCreated an endpoint which return an object. Fetched it in `getFloorInfo()` method and set value of kitchen Object to var `kitchens`. Then check logic of `openKitchenModal` method. The value just dissapears / don't get passed / or event worse when trying to do like this \r\n```js\r\nkitchens.value.forEach((k) => {\r\n if (k.name === kitchen_name) {\r\n kitchen = k\r\n return\r\n }\r\n })\r\n console.log(kitchen)\r\n openedKitchen.value = kitchen\r\n```\r\nit CLEARS OBJECT in the `kitchens`. So that name and other params are \"\" but somehow `id` is keeped\r\n \r\n\r\n\r\n\r\n### Additional context\r\n\r\n Images : \r\n \r\n\r\n\r\n\r\n\r\n\r\n### Logs\r\n\r\n_No response_",[2967,2970,2971],{"name":2968,"color":2969},"3.x","29bc7f",{"name":2933,"color":2934},{"name":2972,"color":2973},"needs reproduction","FBCA04",25405,"Value dissapeared ","2024-03-29T20:54:49Z","https://github.com/nuxt/nuxt/issues/25405",0.7633779,{"description":2980,"labels":2981,"number":2985,"owner":2872,"repository":2873,"state":2887,"title":2986,"updated_at":2987,"url":2988,"score":2989},"### Description\n\nThere is currently no easy way to know what state the modal is in. Adding a `toggle` method would make life very much easier.\n\nI'm willing to make a PR\n\n### Additional context\n\n_No response_",[2982,2983,2984],{"name":2896,"color":2897},{"name":2869,"color":2870},{"name":2900,"color":2901},3720,"feat: add toogle for useOverlay","2025-04-09T15:26:14Z","https://github.com/nuxt/ui/issues/3720",0.7643254,["Reactive",2991],{},["Set"],["ShallowReactive",2994],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f5pvfUehSK9Ju93N3ykU9EuCWgda-JbZVtNmAOpcDE1M":-1},"/nuxt/ui/3374"]