\n\u003C/UDropdownMenu>\n\u003C/template>\n\n\u003Cscript setup lang=\"ts\">\nconst profilePicture = ref('/this/image/does/not/exist.jpg')\nconst items = [\n[{\n\tlabel: 'Logout',\n\ticon: 'i-lucide-log-out',\n}]\n]\n\u003C/script>\n```\n\n### Description\n\nWhen the `src` of the image in `UAvatar` fails to get resolved for any reason (non-existent resource, network error, refused connection from the requested host, etc), it no longer triggers the expansion of the `UDropdownMenu`. \n\nNote that this might also affect `UPopover`, but I have not tested it yet. I will be able to test it later today.\n\nP.S. @benjamincanac this was the reason I initially included it in the migration guide, because I did not know it only happens on non-resolved images\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3187,3188],{"name":3158,"color":3159},{"name":3177,"color":3178},2923,"`UAvatar` with non-resolved `src` fails to trigger `UDropdownMenu`","2025-01-25T13:12:33Z","https://github.com/nuxt/ui/issues/2923",0.6084478,{"description":3195,"labels":3196,"number":3197,"owner":3135,"repository":3198,"state":3149,"title":3199,"updated_at":3200,"url":3201,"score":3202},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.14.0`\n- Nuxt Version: `3.16.0`\n- CLI Version: `3.22.5`\n- Nitro Version: `2.11.5`\n- Package Manager: `bun@1.2.4`\n- Builder: `-`\n- User Config: `runtimeConfig`, `modules`, `app`, `site`, `sitemap`, `robots`, `css`, `icon`, `image`, `ui`, `devtools`, `future`, `unhead`, `compatibilityDate`\n- Runtime Modules: `@nuxt/ui@3.0.0-beta.3`, `@pinia/nuxt@0.10.1`, `@nuxt/scripts@0.10.5`, `@nuxt/image@1.9.0`, `@nuxtjs/seo@2.2.0`\n- Build Modules: `-`\n\n### Reproduction\n\nnda\n\n### Describe the bug\n\nnr dev\n$ nuxt dev\nNuxt 3.16.0 with Nitro 2.11.5 nuxi 8:23:08 PM\n 8:23:08 PM\n ➜ Local: http://localhost:3003/\n ➜ Network: use --host to expose\n\n ➜ DevTools: press Shift + Option + D in the browser (v2.2.1) 8:23:10 PM\n\n\n✔ Nuxt Icon loaded local collection elfi with 70 icons 8:23:10 PM\nℹ Running with compatibility version 4 nuxt 8:23:10 PM\n✔ Vite client built in 190ms 8:23:11 PM\n✔ Vite server built in 528ms 8:23:12 PM\n\n[nitro 8:23:14 PM] ERROR Error: Could not load /\u003Cmy-path>/node_modules/unenv/dist/runtime/runtime/mock/empty.mjs (imported by node_modules/nuxt-og-image/dist/runtime/server/og-image/satori/instances.js): ENOENT: no such file or directory, open '/\u003Cmy-path>/node_modules/unenv/dist/runtime/runtime/mock/empty.mjs'\n\n\nundefined\n\n### Additional context\n\nUpgraded by \"nuxi upgrade -f\" from 3.15.4 and couldn't able to start properly with provided error.\nTried with unhead flag in nuxt.config - same error\n```\nunhead: {\n legacy: true,\n }\n```\n\n### Logs\n\n```shell-script\n\n```",[],414,"scripts","Nuxt 3.16.0 won't start properly nor dev nor build","2025-03-07T18:58:03Z","https://github.com/nuxt/scripts/issues/414",0.6158439,{"description":3204,"labels":3205,"number":3210,"owner":3135,"repository":3167,"state":3149,"title":3211,"updated_at":3212,"url":3213,"score":3214},"### Description\n\nThis is highly experimental and potentially canceled, I'm opening this issue to both track down best approach and naming conventions before working on a PR. **I'll update this issue as I work on it**\n\n## Idea\n\nWith the current [Design Tokens](https://ui3.nuxt.dev/getting-started/theme#tokens) we control colors, radius and container width. This greatly simplifies both prototyping process and agencies working on templates built with Nuxt UI.\nPersonally there is one missing feature about colors: their opacity/shades, that you can find in the various states and variants.\n\nTaking in example any variant for the `Button` component, we have a set of hardcoded opacities (in this case: `/25`, `/10` and `/15`):\nhttps://github.com/nuxt/ui/blob/7f64198a70104436f39f2f9d8527df0508fd84f6/src/theme/button.ts#L91-L95\n\nIn a design first approach, especially when working on bigger projects, it is often to have the brand colors pre-defined for things like hover, disabled and such. This means that, if the project requires them, you are most probably forced to edit each very component's color in the `app.config`.\n\n### What we have\n\nWe auto generate a series of css variables as `--ui-{color}` based on `ui.theme.colors` inside the `nuxt.config.ts`. Then use them as `(text/bg/ring)-[var(--ui-{color})]/{opacity}` both as base and with modifiers (hover, disabled and so on).\n\nThey are used 40 times in total (7 unique: `/10`, `/15`, `/20`, `/25`, `/50`, `/75` and `/90`), distributed as:\n- **24** on `--ui-{color}`\n - ...\n- **7** on `--ui-bg-elevated`\n - `/50` for bg, hover and `data-highlighted`\n- **4** on `--ui-bg-accented`\n - `/75` for hover\n- **3** on `--ui-bg`\n - `/75` for pinned and sticky in UTable\n- **2** on `--ui-bg-inverted`\n - `/20` for `data-[highlighted]`\n - `/90` for hover\n\n### My approach\n\nI would like to group the various opacities into two categories: those that are actual opacities (mainly for `--ui-bg*`) and those that are for colors.\n- for the background ones I would mostly group them as three type of opacities (potentially creating three named variants)\n- for colors I would simply replace them with another named css variable, with follows the naming convention of `--ui-bg-(elevated/inverted/accented/*)`, becoming something like `--ui-{color}-(elevated/inverted/accented/*)`. For its default value I would use `color-mix(oklab, var(--ui-{color}) {opacity});`, keeping the current functionality of requiring a single starting color.\n\n### Additional context\n\n_No response_",[3206,3209],{"name":3207,"color":3208},"enhancement","a2eeef",{"name":3177,"color":3178},2941,"[Design Tokens] add `opacity` modifiers","2025-02-07T15:47:50Z","https://github.com/nuxt/ui/issues/2941",0.6254652,{"description":3216,"labels":3217,"number":3223,"owner":3135,"repository":3167,"state":3149,"title":3224,"updated_at":3225,"url":3226,"score":3227},"### Description\n\nHello, \n\nI was looking for adding Català language to nuxt ui v3. However, i am not used to pull requests but also, the 'ca' code may be confusing with Canada one (and may be others?)\n\nCan someone help me on that way so I will be able to use the locale in the UApp componente :) ?\n\nThank you very much ! \n\n```\n\nimport { defineLocale } from '../composables/defineLocale'\n\nexport default defineLocale({\n name: 'Català',\n code: 'ca',\n messages: {\n inputMenu: {\n noMatch: 'No hi ha dades coincidents',\n noData: 'Sense dades',\n create: 'Crear \"{label}\"'\n },\n calendar: {\n prevYear: 'Any anterior',\n nextYear: 'Any següent',\n prevMonth: 'Mes anterior',\n nextMonth: 'Mes següent'\n },\n inputNumber: {\n increment: 'Incrementar',\n decrement: 'Decrementar'\n },\n commandPalette: {\n placeholder: 'Escriu una ordre o cerca...',\n noMatch: 'No hi ha dades coincidents',\n noData: 'Sense dades',\n close: 'Tancar'\n },\n selectMenu: {\n noMatch: 'No hi ha dades coincidents',\n noData: 'Sense dades',\n create: 'Crear \"{label}\"',\n search: 'Cerca...'\n },\n toast: {\n close: 'Tancar'\n },\n carousel: {\n prev: 'Anterior',\n next: 'Següent',\n goto: 'Anar a la diapositiva {slide}'\n },\n modal: {\n close: 'Tancar'\n },\n slideover: {\n close: 'Tancar'\n },\n alert: {\n close: 'Tancar'\n },\n table: {\n noData: 'Sense dades'\n }\n }\n})\n\n```\n\n### Additional context\n\n_No response_",[3218,3219,3220],{"name":3207,"color":3208},{"name":3177,"color":3178},{"name":3221,"color":3222},"triage","ffffff",3477,"Adding Català language","2025-03-20T14:09:46Z","https://github.com/nuxt/ui/issues/3477",0.62772435,{"description":3229,"labels":3230,"number":3234,"owner":3135,"repository":3167,"state":3149,"title":3235,"updated_at":3236,"url":3237,"score":3238},"### Description\n\nMultiple UCheckbox can share the same v-model by using an array like :\r\n\r\nhttps://vuetifyjs.com/en/components/checkboxes/#colors\r\n\r\n",[3231],{"name":3232,"color":3233},"question","d876e3",1740,"UCheckbox v-model as array","2025-03-31T08:02:40Z","https://github.com/nuxt/ui/issues/1740",0.6485204,{"description":3240,"labels":3241,"number":3243,"owner":3135,"repository":3167,"state":3149,"title":3244,"updated_at":3245,"url":3246,"score":3247},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v18.20.3\r\n- Nuxt Version: 3.13.2\r\n- CLI Version: 3.14.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: pnpm@8.15.6\r\n- Builder: -\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Version\n\nv2.18.6\n\n### Reproduction\n\nhttps://stackblitz.com/~/github.com/Yves852/nuxt-ui-commandpalette-hover\n\n### Description\n\nSelecting an element on click is visually inconsistent. Visually all elements are selected, independantly of `v-model=\"selected\"`.\r\n\r\nWith props `multiple` visually will select all or unselect all, independantly of `v-model=\"selected\"`.\r\n\r\nOn keyboard, using \"enter\" to select update selected correctly but component jump to first element. Same visual problems as mouse.\r\n\r\nThe prop `nullable` doesn't seem to influence the bug.\r\n\r\nRelated to https://github.com/nuxt/ui/issues/2284\r\nCould be related to [1708](https://github.com/nuxt/ui/issues/1708)\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3242],{"name":3158,"color":3159},2285,"CommandPalette: visual item selection inconsistent","2024-11-19T15:26:05Z","https://github.com/nuxt/ui/issues/2285",0.6497747,["Reactive",3249],{},["Set"],["ShallowReactive",3252],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fM0CiYY19v-3mBpsBK4ps9fWOJ7h_P-4Qrvf7OFGRpKo":-1},"/nuxt/ui/2238"]