\n \u003C/template>\n \u003C/USelect>\n \u003C/UFormField>```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2928,2931],{"name":2929,"color":2930},"bug","d73a4a",{"name":2874,"color":2875},3148,"closed","V3 In Select slot trailing","2025-01-25T13:13:41Z","https://github.com/nuxt/ui/issues/3148",0.6883046,{"description":2939,"labels":2940,"number":2943,"owner":2877,"repository":2878,"state":2933,"title":2944,"updated_at":2945,"url":2946,"score":2947},"### Description\n\ncan you add Scroll-area component ? like the one in shadcn \"https://ui.shadcn.com/docs/components/scroll-area\"\n\n### Additional context\n\n_No response_",[2941,2942],{"name":2871,"color":2872},{"name":2874,"color":2875},3425,"Scroll-area","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/3425",0.73288035,{"description":2949,"labels":2950,"number":2957,"owner":2877,"repository":2877,"state":2933,"title":2958,"updated_at":2959,"url":2960,"score":2961},"### Describe the feature\n\nWhen you are behind a reverse proxy that handles HTTPS for you, there should be a way to have a different protocol on the server and on the client for HMR websockets.\r\n\r\nWe already have \"clientPort\", so you can have a different port on the server and in the client.\r\n\r\nThe feature would be a \"clientProtocol\" option, so the server can use \"ws://\" while the client uses \"wss://\".\r\n\r\nUsage:\r\n```javascript\r\n{\r\n vite: {\r\n server: {\r\n hmr: {\r\n protocol: \"wss\",\r\n clientProtocol: \"ws\",\r\n },\r\n },\r\n },\r\n}\r\n```\r\n\r\nThis could also be a solution for issue nuxt/nuxt.js#12003\n\n### Additional information\n\n- [ ] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://v3.nuxtjs.org/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/framework/discussions) and [issues](https://github.com/nuxt/framework/issues).",[2951,2954],{"name":2952,"color":2953},"3.x","29bc7f",{"name":2955,"color":2956},"pending triage","E99695",12408,"Add \"clientProtocol\" option to HMR config","2023-01-19T16:18:48Z","https://github.com/nuxt/nuxt/issues/12408",0.75678205,{"description":2963,"labels":2964,"number":2967,"owner":2877,"repository":2878,"state":2933,"title":2968,"updated_at":2969,"url":2970,"score":2971},"### 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_",[2965,2966],{"name":2871,"color":2872},{"name":2874,"color":2875},2941,"[Design Tokens] add `opacity` modifiers","2025-02-07T15:47:50Z","https://github.com/nuxt/ui/issues/2941",0.76891154,{"description":2973,"labels":2974,"number":2975,"owner":2877,"repository":2976,"state":2933,"title":2977,"updated_at":2978,"url":2979,"score":2980},"## Issue\nIn dev mode contributor images are not rendered as expected on landing page:\n\n\n\n\n## Repro\n1. Run `pnpm dev`\n2. Browse to `http://localhost:3000/` and scroll down to **Built by developers...**\n\n## Root cause\n`nuxt.config.ts` is missing config `$development.image.ipx.baseURL`.",[],1785,"nuxt.com","contributor images on landing page not rendered as expected in dev mode","2025-03-21T16:12:54Z","https://github.com/nuxt/nuxt.com/issues/1785",0.7695929,{"description":2982,"labels":2983,"number":2986,"owner":2877,"repository":2878,"state":2933,"title":2987,"updated_at":2945,"url":2988,"score":2989},"### Environment\n\nHi, I just wanted to share that the styling on the docs website appears broken when viewed in Firefox. I checked on Chrome, and it displays correctly there.\n\nHere’s a screenshot:\n\n\n\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nN/A\n\n### Reproduction\n\nN/A\n\n### Description\n\nN/A\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2984,2985],{"name":2929,"color":2930},{"name":2874,"color":2875},3397,"Nuxt UI v3 docs styling broken","https://github.com/nuxt/ui/issues/3397",0.77166307,["Reactive",2991],{},["Set"],["ShallowReactive",2994],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fYe4RO8fesqX5-KnKecG0B3XkDeMTw9bb51xeH_vztbE":-1},"/nuxt/ui/2861"]