\n```",[3137],{"name":3138,"color":3139},"question","d876e3",4849,"nuxt","ui","open","Can `UNavigationMenu` support active styles via the ui prop?","2025-08-30T10:29:01Z","https://github.com/nuxt/ui/issues/4849",0.71457356,{"description":3149,"labels":3150,"number":3157,"owner":3141,"repository":3142,"state":3143,"title":3158,"updated_at":3159,"url":3160,"score":3161},"### Package\n\nv4.0.0-alpha.x\n\n### Description\n\nIt's currently not possible to disable trailing icons globally or in items for items with children. \nI would like to implement a new prop: disableTrailingIcon(s).\n\nShould this prop appear in NavigationMenuItem too?\n\n### Additional context\n\n_No response_",[3151,3154],{"name":3152,"color":3153},"enhancement","a2eeef",{"name":3155,"color":3156},"triage","ffffff",4847,"[NavigationMenu] disabling trailing Icons globally and/or in NavigationMenuItems.","2025-08-29T20:09:39Z","https://github.com/nuxt/ui/issues/4847",0.7213872,{"description":3163,"labels":3164,"number":3170,"owner":3141,"repository":3142,"state":3143,"title":3171,"updated_at":3172,"url":3173,"score":3174},"### Description\n\nFor [SelectMenu](https://ui.nuxt.com/components/select-menu) seems to be no option to customize the label of the selected item, e.g. use multiple values to compose the label. Currently only one item value can be selected by prop `labelKey`, but it is not possible to use multiple values OR to even add custom html-code.\n\n**Example:**\n\n```ts\nconst items = [\n {\n id: 1,\n firstName: 'Max',\n lastName: 'Mustermann',\n },\n ...\n]\n```\n\nThe items to select can be fully customized, even with custom html code:\n\n```vue\n\u003Ctemplate #item-label=\"{ item }\">\n {{ item.firstName }} \u003Cspan class=\"text-highlighted\">{{ item.lastName}}\u003C/span>\n \u003Cdiv class=\"text-xs text-muted\">#{{ item.customerId }}\u003C/div>\n\u003C/template>\n```\n\nBut when an item is selected, the selected item can only be one value:\n\n```vue\n\u003CUSelectMenu label-key=\"lastName\" />\n```\n\n**Possible solutions:**\n\n1. Make a new label prop that accepts a function, so values can be compound:\n\n```ts\n\u003CUSelectMenu :label=\"(item) => item.firstName + ' ' + item.lastName\"\n```\n\n2. Optionally make a slot to customize the labels: \n```vue\n\u003CUSelectMenu>\n \u003Ctemplate #label=\"{ item }\">\n {{ item.firstName }} \u003Cspan class=\"text-highlighted\">{{ item.lastName}}\u003C/span>\n \u003Cspan class=\"text-xs text-muted\">#{{ item.customerId }}\u003C/span>\n \u003C/template>\n\u003C/USelectMenu>\n```\n\nP.S. the prop `labelKey` is not documented https://ui.nuxt.com/components/select-menu#props\n",[3165,3166,3169],{"name":3152,"color":3153},{"name":3167,"color":3168},"v3","49DCB8",{"name":3155,"color":3156},4581,"SelectMenu: Compound label","2025-07-23T16:38:06Z","https://github.com/nuxt/ui/issues/4581",0.7329244,{"description":3176,"labels":3177,"number":3183,"owner":3141,"repository":3142,"state":3143,"title":3184,"updated_at":3185,"url":3186,"score":3187},"### Environment\n\n\"nuxt\": \"^3.17.5\",\n\"@nuxt/ui\": \"^3.1.3\",\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.1.3\n\n### Reproduction\n\nFollowing is my `components/AppHeader.vue`:\n\n```\n\u003Ctemplate>\n \u003Cheader class=\"bg-white sticky top-0 z-50\">\n \u003Cnav class=\"hidden lg:flex flex-1 justify-center\">\n \u003CUNavigationMenu\n v-model=\"activeSection\"\n :items=\"navItems\"\n class=\"space-x-2\"\n highlight\n highlight-color=\"primary\"\n >\n \u003Ctemplate #item=\"{ item, active }\">\n \u003CULink\n as-child\n :to=\"{ path: '', hash: `#${item.to}` }\"\n exact-hash\n class=\"px-4 py-2 rounded-md transition\"\n aria-label=\"Go to {{ item.label }}\"\n >\n \u003Cspan class=\"inline-flex items-center\">\n \u003CUIcon v-if=\"item.icon\" :name=\"item.icon\" class=\"size-5 mr-2\" />\n \u003Cspan>{{ item.label }}\u003C/span>\n \u003C/span>\n \u003C/ULink>\n \u003C/template>\n \u003C/UNavigationMenu>\n \u003C/nav>\n \u003C/header>\n\u003C/template>\n\n\u003Cscript setup lang=\"ts\">\nimport { ref, watch, onMounted } from \"vue\";\nimport { useRoute } from \"vue-router\";\nimport type { NavigationMenuItem } from \"@nuxt/ui\";\n\nconst route = useRoute();\nconst activeSection = ref(\"\");\n\n// Define your nav data (to = hash without leading '#')\nconst navItems = ref\u003CNavigationMenuItem[]>([\n { label: \"Home\", icon: \"i-lucide-home\", value: \"\", to: \"\" },\n {\n label: \"About Us\",\n icon: \"i-lucide-user-circle\",\n value: \"about\",\n to: \"about\",\n },\n {\n label: \"Products\",\n icon: \"i-lucide-package\",\n value: \"products\",\n to: \"products\",\n },\n {\n label: \"Technologies\",\n icon: \"i-lucide-cpu\",\n value: \"technologies\",\n to: \"technologies\",\n },\n {\n label: \"News\",\n icon: \"i-lucide-newspaper\",\n value: \"news\",\n to: \"news\",\n },\n]);\n\n// On load, seed activeSection from the current hash\nonMounted(() => {\n activeSection.value = route.hash.replace(/^#/, \"\");\n});\n\n// Update when the hash changes\nwatch(\n () => route.hash,\n (h) => {\n activeSection.value = h.replace(/^#/, \"\");\n }\n);\n\u003C/script>\n```\n\n### Description\n\n\nI’m using the Nuxt UI `\u003CUNavigationMenu>` component in my Nuxt 3 app to render a header nav that scrolls to sections via hash links within my `pages/index.vue` (`#about`, `#products`, `#news`, etc.). Clicking works fine, and the correct menu item highlights and scrolls to that section.\n\nHowever, if I reload the page while viewing, for example,`/#products` or any other section like `#news, #about`, etc., the page scrolls to the respective `products/news/about` section, but the navigation menu always highlights `“Home”` (the first item) instead of `Products/News/About`.\n\nHow can I get `\u003CUNavigationMenu>` to pick up the current `route.hash` on load so that the correct item is active?\n\n\n\nFollowing is the documentation I am refeering to:\n\u003CUNavigationMenu> API: [https://ui.nuxt.com/components/navigation-menu][1]\n\n\n [1]: https://ui.nuxt.com/components/navigation-menu\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3178,3181,3182],{"name":3179,"color":3180},"bug","d73a4a",{"name":3167,"color":3168},{"name":3155,"color":3156},4416,"Nuxt 3/Nuxt UI UNavigationMenu won’t highlight hash‐based section on page reload","2025-06-28T10:47:43Z","https://github.com/nuxt/ui/issues/4416",0.73339367,{"description":3189,"labels":3190,"number":3193,"owner":3141,"repository":3142,"state":3194,"title":3195,"updated_at":3196,"url":3197,"score":3198},"### Description\n\nIn the vertical pill variant I want the background of the active item to be white. It's not clear how to achieve this through the `ui` prop\n\n\n\n```\n\u003CUNavigationMenu\n orientation=\"vertical\"\n variant=\"pill\"\n :items=\"items\"\n\n :ui=\"{\n variants: {\n compoundVariants: [\n {\n variant: 'pill',\n active: true,\n highlight: false,\n class: {\n link: 'before:bg-white' // tried this but it's not working\n }\n }\n ]\n }\n }\"\n/>\n```",[3191,3192],{"name":3138,"color":3139},{"name":3167,"color":3168},3517,"closed","How To Style NavigationMenu items","2025-05-10T11:36:22Z","https://github.com/nuxt/ui/issues/3517",0.70182097,{"description":3200,"labels":3201,"number":3209,"owner":3141,"repository":3142,"state":3194,"title":3210,"updated_at":3211,"url":3212,"score":3213},"### Description\n\n## No Clear Documentation for Targeting Active Styles in `NavigationMenu` Component\n\n### Description\n\nI'm trying to apply custom styles to the active state of a menu item in the `NavigationMenu` component, but there doesn't seem to be any clear documentation on how to do this.\n\nThe [theming docs](https://ui.nuxt.com/getting-started/theme#props) mention using the `:ui` attribute to target internal parts of a component, and the [theme structure for `NavigationMenu`](https://ui.nuxt.com/components/navigation-menu#theme) shows a large theme object. However, attempting to follow that structure often results in unexpected behavior—like rendering `[object Object]`, which suggests that it doesn't expect an object or the nested configuration isn’t being parsed correctly.\n\nEven large language models get tripped up when referencing the documentation. Some approaches I've tried (unsuccessfully) include:\n\n```js\nlink: {\n base: 'px-3 py-2 rounded-md',\n active: 'bg-primary text-white font-medium'\n},\nvariants: {\n active: {\n true: {\n item: 'bg-primary text-white font-medium'\n }\n }\n}\n```\n\nThe only working solution so far is using data-* attributes like this:\n```js\nlink: 'text-md data-active:bg-primary data-active:text-white'\n```\nWhile this works, it’s undocumented and feels fragile—it could easily break with a future update if it’s not the intended method.\n\n### Question\nWhat is the official and supported way to apply styles based on active state for subcomponents like link in NavigationMenu?",[3202,3203,3204,3207],{"name":3138,"color":3139},{"name":3167,"color":3168},{"name":3205,"color":3206},"closed-by-bot","ededed",{"name":3208,"color":3206},"stale",4279,"Targeting active menu styles","2025-08-20T02:08:31Z","https://github.com/nuxt/ui/issues/4279",0.7072477,{"description":3215,"labels":3216,"number":3222,"owner":3141,"repository":3142,"state":3194,"title":3223,"updated_at":3224,"url":3225,"score":3226},"### Environment\n\n```\n System:\n OS: macOS 15.5\n CPU: (14) arm64 Apple M3 Max\n Memory: 555.83 MB / 36.00 GB\n Shell: 5.9 - /bin/zsh\n Binaries:\n Node: 23.11.0 - /opt/homebrew/bin/node\n Yarn: 1.22.22 - /opt/homebrew/bin/yarn\n npm: 10.9.2 - /opt/homebrew/bin/npm\n pnpm: 9.12.3 - /opt/homebrew/bin/pnpm\n Watchman: 2025.04.28.00 - /opt/homebrew/bin/watchman\n npmPackages:\n nuxt: ^3.17.3 => 3.17.4 \n```\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.17.4\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/nuxt-ui3-n3sxks\n\n### Description\n\nWhen using the UNavigationMenu component from Nuxt UI 3 in a fresh Nuxt 3 app, the following warning appears in the browser console:\n\n```shell-script\n> [Vue warn] toRefs() expects a reactive object but received a plain one.\n```\n\nThis occurs even when rendering the component barebones:\n\n**pages/index.vue:**\n\n```vue\n\u003Cscript setup lang=\"ts\">\nimport type { NavigationMenuItem } from '@nuxt/ui'\n\nconst items = ref\u003CNavigationMenuItem[]>([\n {\n label: 'Guide',\n icon: 'i-lucide-book-open',\n to: '/getting-started',\n children: [\n {\n label: 'Introduction',\n description: 'Fully styled and customizable components for Nuxt.',\n icon: 'i-lucide-house'\n },\n {\n label: 'Installation',\n description: 'Learn how to install and configure Nuxt UI in your application.',\n icon: 'i-lucide-cloud-download'\n },\n {\n label: 'Icons',\n icon: 'i-lucide-smile',\n description: 'You have nothing to do, @nuxt/icon will handle it automatically.'\n },\n {\n label: 'Colors',\n icon: 'i-lucide-swatch-book',\n description: 'Choose a primary and a neutral color from your Tailwind CSS theme.'\n },\n {\n label: 'Theme',\n icon: 'i-lucide-cog',\n description: 'You can customize components by using the `class` / `ui` props or in your app.config.ts.'\n }\n ]\n },\n {\n label: 'Composables',\n icon: 'i-lucide-database',\n to: '/composables',\n children: [\n {\n label: 'defineShortcuts',\n icon: 'i-lucide-file-text',\n description: 'Define shortcuts for your application.',\n to: '/composables/define-shortcuts'\n },\n {\n label: 'useOverlay',\n icon: 'i-lucide-file-text',\n description: 'Display a modal/slideover within your application.',\n to: '/composables/use-overlay'\n },\n {\n label: 'useToast',\n icon: 'i-lucide-file-text',\n description: 'Display a toast within your application.',\n to: '/composables/use-toast'\n }\n ]\n },\n {\n label: 'Components',\n icon: 'i-lucide-box',\n to: '/components',\n active: true,\n children: [\n {\n label: 'Link',\n icon: 'i-lucide-file-text',\n description: 'Use NuxtLink with superpowers.',\n to: '/components/link'\n },\n {\n label: 'Modal',\n icon: 'i-lucide-file-text',\n description: 'Display a modal within your application.',\n to: '/components/modal'\n },\n {\n label: 'NavigationMenu',\n icon: 'i-lucide-file-text',\n description: 'Display a list of links.',\n to: '/components/navigation-menu'\n },\n {\n label: 'Pagination',\n icon: 'i-lucide-file-text',\n description: 'Display a list of pages.',\n to: '/components/pagination'\n },\n {\n label: 'Popover',\n icon: 'i-lucide-file-text',\n description: 'Display a non-modal dialog that floats around a trigger element.',\n to: '/components/popover'\n },\n {\n label: 'Progress',\n icon: 'i-lucide-file-text',\n description: 'Show a horizontal bar to indicate task progression.',\n to: '/components/progress'\n }\n ]\n },\n {\n label: 'GitHub',\n icon: 'i-simple-icons-github',\n badge: '3.8k',\n to: 'https://github.com/nuxt/ui',\n target: '_blank'\n },\n {\n label: 'Help',\n icon: 'i-lucide-circle-help',\n disabled: true\n }\n])\n\u003C/script>\n\u003Ctemplate>\n \u003CUNavigationMenu :items=\"items\" class=\"w-full justify-center\" />\n\u003C/template>\n\n```\n\n**Minimal Reproduction**\nRepro created using Nuxt 3 + Nuxt UI 3 starter structure.\n\npackage.json:\n```json\n{\n \"name\": \"nuxt-app\",\n \"private\": true,\n \"type\": \"module\",\n \"scripts\": {\n \"build\": \"nuxt build\",\n \"dev\": \"nuxt dev\",\n \"generate\": \"nuxt generate\",\n \"preview\": \"nuxt preview\",\n \"postinstall\": \"nuxt prepare\",\n \"lint\": \"eslint .\",\n \"lint:fix\": \"eslint --fix .\"\n },\n \"dependencies\": {\n \"@iconify-json/lucide\": \"^1.2.44\",\n \"@iconify-json/simple-icons\": \"^1.2.35\",\n \"@nuxt/ui\": \"^3.1.1\",\n \"nuxt\": \"^3.17.3\"\n },\n \"devDependencies\": {\n \"@nuxt/eslint\": \"^1.4.1\",\n \"eslint\": \"^9.27.0\",\n \"typescript\": \"^5.8.3\"\n }\n}\n```\n\nNotes\n\t•\tReproduces consistently in local dev.\n\t•\tDoes not reproduce on Codesandbox with the Nuxt UI 3 starter (possibly due to different runtime setup).\n\t•\tNo functional issues observed so far, but the warning pollutes the console.\n\t•\tThis warning has only recently started appearing in the console logs, despite no code changes to this component on our end — possibly introduced in a recent dependency update.\n",[3217,3218,3219],{"name":3179,"color":3180},{"name":3167,"color":3168},{"name":3220,"color":3221},"reka-ui","56d799",4257,"[Vue warn] toRefs() expects a reactive object but received a plain one - \u003CUNavigationMenu />","2025-06-10T14:16:02Z","https://github.com/nuxt/ui/issues/4257",0.72243965,{"description":3228,"labels":3229,"number":3234,"owner":3141,"repository":3142,"state":3194,"title":3235,"updated_at":3236,"url":3237,"score":3238},"### Description\n\nHey! Thanks for trying to make nuxt/ui even more awesome.\n\nI've been struggled with adding NavigationMenu items animation on toggling collapsed of/off states. \nI'd like to make it work smoothly and keep only icons with popovers in collapsed state and show the rest only when collapsed is off. out of the box its only toggled on/off without transitions.\nI see no option to pass slot to wrap labels with vue Transition component or use Motion-vue and either css animations like data-[collaped=true]:animate.... not working well because whole inner content of nav is wrapped with \"v-if\" and switched on collapsed. \n\nIn some components data-[state] animations works well, but not in collapsed NavigationMenu. Or am I doing something wrong?\nOnly a way I see is to override whole item slot. But for now I've just get rid of NavigationMenu and made my own custom component with fancy transitions.\nPlease point me to right direction and suggest best practices, cuz I'd like to use most of components and make it work with smooth transitions/animations, but sometimes got stucked with limitations/lack of knowledge. \n\nofftop: For example, wasted many hours trying to achieve smooth slide-down transition for table expanded rows. Ended up with expanded slot with UCollapsible plus exclusive inner state for it, changed with setTimeout(() => { ... }, 300), Ugly, hucky, but it works.",[3230,3231,3232,3233],{"name":3138,"color":3139},{"name":3167,"color":3168},{"name":3205,"color":3206},{"name":3208,"color":3206},4254,"NavigationMenu transitions/animations on toggle collapsed state","2025-08-20T02:08:33Z","https://github.com/nuxt/ui/issues/4254",0.72513926,{"description":3240,"labels":3241,"number":3245,"owner":3141,"repository":3141,"state":3194,"title":3246,"updated_at":3247,"url":3248,"score":3249},"### Environment\n\nLinux `6.16.5-arch1-1` with nuxt `4.1.1`. \nBrowser used: Librewolf 142.0.1-1 and Chrome 139.0.7258.154\n\n```\n- Operating System: `Linux`\n- Node Version: `v22.13.0`\n- Nuxt Version: `4.1.1`\n- CLI Version: `3.28.0`\n- Nitro Version: `2.12.5`\n- Package Manager: `npm@10.9.2`\n- Builder: `-`\n- User Config: `-`\n- Runtime Modules: `-`\n- Build Modules: `-`\n```\n\n### Reproduction\n\nBarebones code example to reproduce this issue, no styling. \nIf you add Tailwind styling the issue becomes even more prominent, as the styling of the inner button gets applied to the outer button, breaking the layout entirely.\n\nI couldn't get any of the two code sandboxes to work, sorry, so here is the code directly:\n\n```vue\n\u003Ctemplate>\n \u003Cdiv>\n\n \u003Cbutton v-for=\"thisItem in storedItems\" :key=\"thisItem.id\">\n \u003Clabel>{{ thisItem.title }}\u003C/label>\n\n \u003Cdiv>\n \u003Cbutton v-for=\"thisLabel in thisItem.labels\" :key=\"thisLabel.id\">\n {{ thisLabel.name }}\n \u003C/button>\n \u003C/div>\n \u003C/button>\n\n \u003C/div>\n\u003C/template>\n\n\n\u003Cscript setup>\n\nconst storedItems = ref([{\n id: \"0\",\n title: \"0\",\n addedTimestamp: Date.now(),\n labels: [\n {\n id: \"0\",\n name: \"Summer\",\n type: \"season\"\n },\n {\n id: \"1\",\n name: \"Cocktail Dress\",\n type: \"type\"\n },\n {\n id: \"2\",\n name: \"2025\",\n type: \"year\"\n },\n {\n id: \"3\",\n name: \"Special\",\n type: \"occasion\"\n },\n {\n id: \"4\",\n name: \"Red\",\n type: \"color\"\n }\n ]\n },\n {\n id: \"1\",\n title: \"1\",\n addedTimestamp: Date.now(),\n labels: [\n {\n id: \"0\",\n name: \"Summer\",\n type: \"season\"\n },\n {\n id: \"1\",\n name: \"Cocktail Dress\",\n type: \"type\"\n },\n {\n id: \"2\",\n name: \"2025\",\n type: \"year\"\n },\n {\n id: \"3\",\n name: \"Special\",\n type: \"occasion\"\n },\n {\n id: \"4\",\n name: \"Red\",\n type: \"color\"\n }\n ]\n },\n {\n id: \"2\",\n title: \"2\",\n addedTimestamp: Date.now(),\n labels: [\n {\n id: \"0\",\n name: \"Summer\",\n type: \"season\"\n },\n {\n id: \"1\",\n name: \"Cocktail Dress\",\n type: \"type\"\n },\n {\n id: \"2\",\n name: \"2025\",\n type: \"year\"\n },\n {\n id: \"3\",\n name: \"Special\",\n type: \"occasion\"\n },\n {\n id: \"4\",\n name: \"Red\",\n type: \"color\"\n }\n ]\n }\n]);\n\n\u003C/script>\n```\n\n### Describe the bug\n\nTwo button elements, nested inside of each other, each containing a `v-for` instruction, causes the layout to break. \nThe for loop is executed an incorrect amount of times and the styling of the inner button can get applied to the outer button, starting with iteration >0.\n\nChanging one of the two button elements to a div/anchor/... fixes the issue.\n\n### Additional context\n\nThis is how it looks on page load:\n\u003Cimg width=\"1196\" height=\"649\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/520c3c98-61c7-4b40-9b97-a634d13d3e2f\" />\n\nThis is how it looks after a hot reload and *should* look:\n\u003Cimg width=\"1196\" height=\"649\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/99a6c586-13e4-4ff6-84f7-b79c4e301844\" />\n\nThe behavior does not change in \"build\" mode, so without the dev server. It technically is even worse because there is no hot-reload to circumvent the issue anymore.\n\n \n\nThis is how it looks in my app with Tailwind styling ^-^:\n\u003Cimg width=\"1849\" height=\"1171\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/e73db657-9526-418a-b611-772a73a4a22f\" />\n\n...and this is how it should look like:\n\u003Cimg width=\"1837\" height=\"1167\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/b34dd8fe-e625-4c84-9666-e46afd238b23\" />\n\n### Logs\n\n```shell-script\n\n```",[3242],{"name":3243,"color":3244},"pending triage","E99695",33188,"Nested button elements with v-for loop are processed incorrectly and break layout","2025-09-09T19:05:58Z","https://github.com/nuxt/nuxt/issues/33188",0.7253748,{"description":3251,"labels":3252,"number":3257,"owner":3141,"repository":3142,"state":3194,"title":3258,"updated_at":3259,"url":3260,"score":3261},"I currently have the problem that we have to integrate our SPA into a larger application. And with that, we also inherit the CSS of the outer application. And that's where it gets really ugly: they have partially written classes in their own CSS files that use the TW naming scheme (m, p, gap, shadow, etc.), and then add `!important` to these declarations. \n\nOne of the big problems with Nuxt UI is that there is no prefixing of Tailwind classes. So we started writing TW utilities with a prefix for the affected classes. This is then transferred to app.config. The second problem was the merge process that app.config uses. Usually the names have to match. If I want to have a `p-4` from the config (because px values with !important were entered in the outer CSS), I created the class `p-00`, which replaces the `p-4` class and thus clears the way for the prefixed TW class `o-p-4`.\n\nSo far so good, but I can't use it with popovers like SelectMenu. No matter what I do, the class `shadow-lg` remains. The other devs of the main application have entered a rather ugly shadow with important there. \n\nIs there another prop like 'content' that I can use to replace `shadow-lg`? I'm not a fan of `!important`, but at this point I can only work this way.\n\nFurthermore, it would be really nice if you could really overwrite the sections in app.config instead of just merging them (apart from prefixing the TW classes). There are certain stylings that you won't use, but then they are in the element",[3253,3254,3255,3256],{"name":3138,"color":3139},{"name":3167,"color":3168},{"name":3205,"color":3206},{"name":3208,"color":3206},3874,"Changing Shadow Classes on Popover and SelectMenu","2025-08-12T02:12:50Z","https://github.com/nuxt/ui/issues/3874",0.72769743,["Reactive",3263],{},["Set"],["ShallowReactive",3266],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fN43deAm0F8ZZj-aLECYdhpXRASf8GJgZNWrUoIvFlnk":-1},"/nuxt/ui/3683"]