\n\n\u003CUInputMenu :items=\"placeItems\"\n value-key=\"id\"\n label-key=\"name\"\n class=\"w-full\"/>\n\u003C/template>\n```\n\n### Description\nIn my opinion, the border, when focusing, should have the same color as when the parameter is absent `multiple`.\nWith white border looks bad :D\nhttps://skr.sh/vSqjqLYGgHO",[1997,2000],{"name":1998,"color":1999},"bug","d73a4a",{"name":2001,"color":2002},"v3","49DCB8",2742,"ui","closed","UInputMenu has wrong border when focused in multiple mode","2024-12-05T13:48:56Z","https://github.com/nuxt/ui/issues/2742",0.66747856,{"description":2011,"labels":2012,"number":2017,"owner":1988,"repository":2004,"state":2005,"title":2018,"updated_at":2019,"url":2020,"score":2021},"### Description\n\nI'm trying to apply styling to specific elements, this is my current code for initializing my NavigationMenu items:\n```js\nconst items = ref\u003CNavigationMenuItem[]>([\n [\n {\n label: \"Something\",\n icon: \"\",\n to: \"/\"\n }\n ],\n [\n {\n icon: \"i-simple-icons-discord\",\n to: \"https://discord.gg/....\"\n }\n ]\n ])\n```\n\nI am trying to apply styling using tailwind like you would via `:ui=\"\"` on the `UNavigationMenu` element but in this case I want to change `linkLeadingIcon` only for the discord element, and replace `list` entirely for the `Something` element. I've been scouring the docs and such and I haven't been able to really find a way to do this. As far as I can tell I can't do styling based on label/icon/etc using compound variants.\n\nI'm fairly new to Nuxt UI so might be missing a obvious solution, thanks!",[2013,2016],{"name":2014,"color":2015},"question","d876e3",{"name":2001,"color":2002},3683,"NavigationMenu styling for specific items","2025-04-18T18:47:43Z","https://github.com/nuxt/ui/issues/3683",0.7112095,{"labels":2023,"number":2028,"owner":1988,"repository":1988,"state":2005,"title":2029,"updated_at":2030,"url":2031,"score":2032},[2024,2027],{"name":2025,"color":2026},"3.x","29bc7f",{"name":1998,"color":1999},12266,"[Vue warn]: Hydration node mismatch:","2024-10-25T10:19:24Z","https://github.com/nuxt/nuxt/issues/12266",0.7213798,{"labels":2034,"number":2042,"owner":1988,"repository":1988,"state":2005,"title":2043,"updated_at":2044,"url":2045,"score":2046},[2035,2038,2039],{"name":2036,"color":2037},"stale","ffffff",{"name":1985,"color":1986},{"name":2040,"color":2041},"2.x","d4c5f9",9973,"Minor bug: CSS with pseudo class with params when staticly generated is different from development","2023-01-22T15:45:05Z","https://github.com/nuxt/nuxt/issues/9973",0.7245375,{"description":2048,"labels":2049,"number":2058,"owner":1988,"repository":1988,"state":2005,"title":2059,"updated_at":2060,"url":2061,"score":2062},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v16.20.0\r\n- Nuxt Version: 3.7.1\r\n- CLI Version: 3.7.3\r\n- Nitro Version: 2.6.2\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: experimental\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Reproduction\n\nYou can use my old preproduction from #23051 https://stackblitz.com/edit/github-ydxe3t?file=pages%2Findex.vue\r\n\r\nSee that the scoped style (margin) applies to the component. However, if you update Nuxt to 3.7.3, the style no longer applies, since the data-v attribute was removed. \n\n### Describe the bug\n\nThe issue #23051 was fixed in #23095.\r\n\r\nHowever, this prevented scoped style from being applied to the component. \r\n\n\n### Additional context\n\nSorry for the delayed feedback. As I noted in https://github.com/nuxt/nuxt/pull/23095#issuecomment-1712583276 the removal of data-v attribute entirely lead to styles not being reproduced. I already debugged the issue and I'm going to create a PR with a simple suggested fix.\r\n\r\nThis PR will revert the expected behavior of scoped styles as in 3.7.1 while keeping @huang-julien 's fix for 404 on soft navigation due to different component hash.\n\n### Logs\n\n_No response_",[2050,2051,2052,2055],{"name":2025,"color":2026},{"name":1998,"color":1999},{"name":2053,"color":2054},"🔨 p3-minor","FBCA04",{"name":2056,"color":2057},"server components","839413",23385,"Fix for #23051 broke scoped styles in server components","2023-09-28T07:36:15Z","https://github.com/nuxt/nuxt/issues/23385",0.72796035,{"description":2064,"labels":2065,"number":2072,"owner":1988,"repository":2073,"state":2005,"title":2074,"updated_at":2075,"url":2076,"score":2077},"",[2066,2069],{"name":2067,"color":2068},"enhancement","a2eeef",{"name":2070,"color":2071},"provider","1161A4",11,"fonts","adobe fonts provider","2024-03-12T23:29:19Z","https://github.com/nuxt/fonts/issues/11",0.7288285,{"labels":2079,"number":2082,"owner":1988,"repository":1988,"state":2005,"title":2083,"updated_at":2084,"url":2085,"score":2086},[2080,2081],{"name":2025,"color":2026},{"name":1998,"color":1999},12669,"Invalid result of `Style` component","2023-01-19T16:09:47Z","https://github.com/nuxt/nuxt/issues/12669",0.7289999,{"description":2088,"labels":2089,"number":2095,"owner":1988,"repository":1988,"state":2005,"title":2096,"updated_at":2097,"url":2098,"score":2099},"### Environment\r\n\r\n- Operating System: Linux\r\n- Node Version: v18.17.0\r\n- Nuxt Version: 3.10.0\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@9.6.7\r\n- Builder: -\r\n- User Config: devtools, postcss, css\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\nCheck out this commit, run `npm run dev` and add pairs:\r\n\r\nhttps://github.com/mktcode/trading-assistant/commit/0ef592d39133d7af8030331b894a95727af117d9\r\n\r\nThe second pair has wrong classes. It's missing the classes of the wrapper div and the button is blue instead of red.\r\nIf you remove the PairSelect component or wrap it in another element, it fixes the display issue. So it has something to do with it. But what?\r\n\r\n### Describe the bug\r\n\r\n\r\n\r\nFor some reason classes aren't applied correctly in this v-for loop of a custom component. If it was the first or last element I could think of a reason but the second element just weirdly not having the classes.... I'm a bit puzzled. Maybe it's because it's monday but maybe it's because of Nuxt doing something weird? Idk. Maybe it's not even nuxt but Vue itself.\r\n\r\n\r\n\r\nIt's always the second div that takes the classes of the select component.\r\n\r\nIt is because the v-for is not wrapped in it's own parent element but I think I never had such a weird issue with that.",[2090,2091,2092],{"name":2025,"color":2026},{"name":1985,"color":1986},{"name":2093,"color":2094},"upstream","E8A36D",25626,"Tailwind classes missing in v-for loop.","2024-02-05T11:55:12Z","https://github.com/nuxt/nuxt/issues/25626",0.729588,{"labels":2101,"number":2104,"owner":1988,"repository":1988,"state":2005,"title":2105,"updated_at":2106,"url":2107,"score":2108},[2102,2103],{"name":1985,"color":1986},{"name":2040,"color":2041},10231,"Bug of hydration children for html elements","2023-01-22T15:45:12Z","https://github.com/nuxt/nuxt/issues/10231",0.730571,["Reactive",2110],{},["Set"],["ShallowReactive",2113],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"C3ZUHSFngBH2bvCcnuBhYmN0VibcmLH0GjRgG6hnr1E":-1},"/nuxt/ui/2766"]