\n\nBrowser: `Google Chrome Version 134.0.6998.89 (Official Build) (arm64)`\n\nAlso reproduced on `Safari Version 18.3.1 (20620.2.4.11.6)`\n\n### Description\n\nUser may want to copy the text in the query input of a `select-menu` component by moving cursor around text, now it's unable to do it without a keyboard (`Shift + left/right arrow` or `Cmd/Ctrl + A` to select all).\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2884,2885],{"name":2868,"color":2869},{"name":2871,"color":2872},3583,"Accessibility: unable to select text in the query input of a select-menu","2025-03-17T00:34:07Z","https://github.com/nuxt/ui/issues/3583",0.68359804,{"description":2892,"labels":2893,"number":2901,"owner":2874,"repository":2875,"state":2876,"title":2902,"updated_at":2903,"url":2904,"score":2905},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.x\n\n### Description\n\nHello everyone, I’d like to discuss the possibility of setting `props` by default from `AppConfig`. Currently, it’s very convenient that we can configure the theme through the config. It would be great to have a similar option for props. Previously, @benjamincanac mentioned [here](https://github.com/nuxt/ui/issues/1289#issuecomment-2480556540) that this is not currently planned.\n\nMy proposal is simple: wrap all `withDefaults` in our own implementation. This way, we can define props without making significant changes to the code.\n\n## What it could look like\n\nLet’s look at the `Accordion.vue` component. At the moment, its props look like this:\n```ts\nconst props = withDefaults(defineProps\u003CAccordionProps\u003CT>>(), {\n type: 'single',\n collapsible: true,\n labelKey: 'label'\n})\n```\nLet’s assume our wrapper is called `withUiDefaults`. Then the code would look like this:\n```diff\n-const props = withDefaults(defineProps\u003CAccordionProps\u003CT>>(), {\n+const props = withUiDefaults(defineProps\u003CAccordionProps\u003CT>>(), {\n type: 'single',\n collapsible: true,\n labelKey: 'label'\n})\n```\nThe implementation of `withUiDefaults` is quite simple:\n```ts\nfunction withUiDefaults(props, defaults) {\n const defaultFromConfig = {}\n\n return withDefaults(props, {\n ...defaults,\n ...defaultFromConfig\n })\n}\n``` \n\n## Issues I See\n\n1) **Typing `AppConfig` might be challenging** \n We would need to somehow generate types based on the components. \n **My opinion:** I think we can retrieve this using `vue-component-meta` during the UI build stage. So, in my opinion, this isn’t a significant problem.\n\n2) **Developers might set `modelValue` or other critical props by default** \n **My opinion:** In such cases, we can log a warning to the console. Additionally, developers should understand which props they are overriding. We won’t be able to cover all edge cases, but I don’t think we need to.\n\n### Additional context\n\n_No response_",[2894,2897,2900],{"name":2895,"color":2896},"enhancement","a2eeef",{"name":2898,"color":2899},"v3","49DCB8",{"name":2871,"color":2872},2662,"Override default props from `AppConfig`","2024-11-17T08:30:46Z","https://github.com/nuxt/ui/issues/2662",0.68749636,{"description":2907,"labels":2908,"number":2911,"owner":2874,"repository":2875,"state":2912,"title":2913,"updated_at":2914,"url":2915,"score":2916},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.x\n\n### Description\n\n[CommandPalette](https://ui3.nuxt.dev/components/command-palette) is great but I wish it could display only an input by default and then open the content in a popper when clicking in the input. I think this is currently not possible but a very common use case. \n\nThis is what I would like to archive, screenshots from Shopify:\n\n\n\n\n\n\n\n### Additional context\n\n_No response_",[2909,2910],{"name":2895,"color":2896},{"name":2898,"color":2899},2832,"closed","v3 CommandPalette: Open only content within popper","2024-12-05T13:24:12Z","https://github.com/nuxt/ui/issues/2832",0.6594953,{"description":2918,"labels":2919,"number":2925,"owner":2874,"repository":2875,"state":2912,"title":2926,"updated_at":2927,"url":2928,"score":2929},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.4.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.16.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.15.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.10, nuxt-auth-sanctum@0.5.2, @vueuse/nuxt@11.3.0, nuxt-file-storage@0.2.9\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.0-alpha.10\n\n### Reproduction\n\n```vue\n\u003Cscript setup lang=\"ts\">\n const place = ref({\n day: 1\n })\n\n const days = ref([\n {\n value: 1,\n label: 'Day 1'\n },\n {\n value: 2,\n label: 'Day 2'\n }\n ])\n\u003C/script>\n\n\u003Ctemplate>\n Place:\n \u003Cpre>{{ place }}\u003C/pre>\n \u003CUSelect v-model=\"place.day\" :items=\"days\" class=\"w-32\" />\n\u003C/template>\n```\n\n### Description\n\nhttps://skr.sh/vT9fUh9cK0d\n\nAfter change `1` transforms to `\"1\"` and got error in console.",[2920,2921,2924],{"name":2868,"color":2869},{"name":2922,"color":2923},"duplicate","cfd3d7",{"name":2898,"color":2899},2886,"USelect converts integer value to string","2025-01-09T14:22:11Z","https://github.com/nuxt/ui/issues/2886",0.671276,{"description":2931,"labels":2932,"number":2933,"owner":2874,"repository":2934,"state":2912,"title":2935,"updated_at":2936,"url":2937,"score":2938},"Open https://nuxt.com/docs/guide/directory-structure/composables, **Introduction** page is shown instead of **Composables**\n\n\n\nI think the regression is due to 43b0f43",[],1752,"nuxt.com","All docs/[...slug] routes show Introduction page","2025-01-14T11:25:53Z","https://github.com/nuxt/nuxt.com/issues/1752",0.6729332,{"description":2940,"labels":2941,"number":2942,"owner":2874,"repository":2943,"state":2912,"title":2944,"updated_at":2945,"url":2946,"score":2947},"Docs: https://posthog.com/docs/libraries/js\r\n\r\nFor reference this is how I currently instrument it:\r\n\r\n```\r\nimport { Capacitor } from '@capacitor/core'\r\nimport { posthog } from 'posthog-js'\r\nimport { appVersion } from '~/shared/version'\r\n\r\nexport default defineNuxtPlugin({\r\n name: 'analytics',\r\n setup() {\r\n if (import.meta.env.TEST) {\r\n return\r\n }\r\n\r\n const config = useRuntimeConfig()\r\n const router = useRouter()\r\n\r\n if (config.public.analyticsReportingEnabled) {\r\n posthog.init(config.public.posthog.dsn, {\r\n capture_pageview: false,\r\n capture_pageleave: true,\r\n api_host: config.public.posthog.apiHost,\r\n disable_session_recording: true,\r\n advanced_disable_decide: true,\r\n advanced_disable_feature_flags: true,\r\n advanced_disable_feature_flags_on_first_load: true,\r\n enable_recording_console_log: false,\r\n autocapture: false\r\n })\r\n\r\n posthog.register({\r\n environment: config.public.appEnvironment,\r\n countryCode: config.public.appCountryCode,\r\n release: appVersion,\r\n platform: Capacitor.getPlatform(),\r\n native: Capacitor.isNativePlatform()\r\n })\r\n\r\n router.afterEach(to => {\r\n posthog.capture('$pageview', {\r\n $current_url: to.fullPath\r\n })\r\n })\r\n }\r\n\r\n return {\r\n provide: {\r\n analytics: posthog\r\n }\r\n }\r\n }\r\n})\r\n```\r\n\r\nand after the user has logged in or we detect they are already logged in on page load:\r\n\r\n```\r\nthis.analytics.identify(userId, {\r\n email\r\n roles\r\n})\r\n ```\r\n \r\n Thanks!\r\n\r\n",[],206,"scripts","Suggestion: Posthog [analytics]","2024-09-03T16:06:49Z","https://github.com/nuxt/scripts/issues/206",0.68008447,{"description":2949,"labels":2950,"number":2955,"owner":2874,"repository":2956,"state":2912,"title":2957,"updated_at":2958,"url":2959,"score":2960},"I've explored other font providers, looks like `fontsource` is also quite promising.\r\n\r\nCurrently most of its fonts are from Google Fonts, along with some icons and some other fonts. It's also the service that Cloudflare Fonts is fetching from.\r\n\r\n@danielroe Would you like to include this font provider? If so, I'd like to work on it.\r\n\r\nDocs: https://fontsource.org/docs",[2951,2952],{"name":2895,"color":2896},{"name":2953,"color":2954},"provider","1161A4",65,"fonts","feat: fontsource provider","2024-03-20T13:12:12Z","https://github.com/nuxt/fonts/issues/65",0.68269897,{"description":2962,"labels":2963,"number":2967,"owner":2874,"repository":2968,"state":2912,"title":2969,"updated_at":2970,"url":2971,"score":2972},"While working on a new project with new developers we stumbled upon this silent failure.\r\nWe had Icons exported from Figma in the format:\r\n\r\n- iconCalendar.svg\r\n- iconPerson.svg\r\n- ...\r\n\r\nWhich were then loaded as customCollection via NuxtConfig\r\n\r\n```\r\nicon: {\r\n customCollections: [\r\n {\r\n prefix: 'theme-icon',\r\n dir: './assets/icons'\r\n },\r\n ],\r\n },\r\n```\r\n\r\nThe message upon restart was reassuring that all icons were loaded and should be accessible.\r\n\r\n```\r\nNuxt Icon loaded local collection theme-icon with 43 icons.\r\n```\r\n\r\n\r\nBut we could not access them, or better said, we could only access the ones which only were lowercase. So I digged down the whole integration with the following waypoints:\r\n\r\n- https://github.com/nuxt/icon/blob/main/src/collections.ts\r\n- https://github.com/nuxt/icon/blob/main/src/runtime/components/svg.ts#L41\r\n- https://github.com/iconify/iconify/blob/main/components/vue/src/iconify.ts#L18\r\n- https://github.com/iconify/iconify/blob/main/packages/core/src/storage/functions.ts#L86\r\n- https://github.com/iconify/iconify/blob/main/packages/utils/src/icon/name.ts#L23\r\n- https://github.com/iconify/iconify/blob/main/packages/utils/src/icon/name.ts#L90\r\n\r\nIn words:\r\n\r\n- The collection gets loaded and auto-detects all svg files within the collection folder. It also validates if the content is valid and loads them into the internal collection of nuxt-icon. \r\n- Then when called by the Component integration it gets converted/added to the Iconify component which then goes down its library path to add it to the/a custom collection for display.\r\n- This in fact validates the name given and will NOT add it if its invalid thus not displaying any icon with invalid names.\r\n- No error handling is done for this in the Component (addIcon in fact returns success which could be handled)\r\n- No validation is done when creating/loading the nuxt-icon collection.\r\n\r\n---\r\n\r\n**Suggested resolution:** For better DX there should also be a name validation when loading the collection and it should warn about all icons not following the convention. I can craft the corresponding PR.\r\n\r\n---\r\n\r\nDid I miss something elsewhere or is my deduction of the error correct?",[2964],{"name":2965,"color":2966},"upstream","B4199A",257,"icon","Invalid Icon filenames, as defined/validated by Iconify, are silently failing","2024-11-21T18:24:05Z","https://github.com/nuxt/icon/issues/257",0.68435055,{"description":2974,"labels":2975,"number":2978,"owner":2874,"repository":2875,"state":2912,"title":2979,"updated_at":2980,"url":2981,"score":2982},"### Description\n\nNuxt UI should have the potential to open native links in a Nuxt UI Modal by simply adding a certain `modal` parameter in [NuxtLink](https://nuxt.com/docs/api/components/nuxt-link).\n\n`\u003CNuxtLink to=\"/about\" modal>About page shown in modal but can also be opened natively (e.g. new tab)\u003C/NuxtLink>`\n\nThe link should still be a native link with progressive enhancement, so _if users would like to open the URL in a new tab, they can do_! If not, it will open the content in a modal.\n\nThat would be great DX and UX! 🎉\n\nThe `modal` property is just one possible solution, maybe there's even a better one using a native HTML property like `rel=\"modal\"`, we should discuss that.\n\nIn future versions there might be further control parameters to override the defaults for\n\n- modal size\n- modal style\n- modal opacity\n- ...\n\nBut let's start simple.\n\nSomething similar was done here, but I think this should really be part of Nuxt UI or even Nuxt Core.\nhttps://nuxt-pages-plus.pages.dev/components/plus-modal-link\n\n### Additional context\n\n_No response_",[2976,2977],{"name":2895,"color":2896},{"name":2898,"color":2899},3298,"Enhance NuxtLink to open in Modal using a \"modal\" property","2025-03-08T12:21:53Z","https://github.com/nuxt/ui/issues/3298",0.6869145,["Reactive",2984],{},["Set"],["ShallowReactive",2987],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fLuMRN_dsiu5gQ5-6dZ6SCt8bjqkvqSe8c-MR0MmLlPQ":-1},"/nuxt/ui/2805"]