` for the rest of the content, which could be either 1 or more DashboardPanels.\n\nThanks in advance!",[2914,2917,2918],{"name":2915,"color":2916},"question","d876e3",{"name":2869,"color":2870},{"name":2919,"color":2920},"pro","5BD3CB",3627,"How to add a persistent Navbar on top of all DashboardPanels inside of a DashboardGroup?","2025-03-19T20:53:14Z","https://github.com/nuxt/ui/issues/3627",0.6918338,{"description":2927,"labels":2928,"number":2931,"owner":2875,"repository":2876,"state":2906,"title":2932,"updated_at":2933,"url":2934,"score":2935},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.x\n\n### Description\n\nI find that creating an input password with toggle button to show the text felt so verbose. How about adding a default toggle button when the input has password type since it was a good practice for accessibility?\n\n\n\n### Additional context\n\n```html\n\u003C!-- this is easier and shorter to write -->\n\u003CUInput type=\"password\" />\n\n\u003C!-- if we want to hide, we can let slot do the work, or maybe consider adding a properties to hide it. It's more shorter -->\n\u003CUInput type=\"password\">\n \u003Ctemplate #trailing>\u003C/template>\n\u003C/UInput>\n\n\u003C!-- compared to what we must do now as the documentation say -->\n\u003Ctemplate>\n \u003CUInput\n v-model=\"password\"\n placeholder=\"Password\"\n :type=\"show ? 'text' : 'password'\"\n :ui=\"{ trailing: 'pe-1' }\"\n >\n \u003Ctemplate #trailing>\n \u003CUButton\n color=\"neutral\"\n variant=\"link\"\n size=\"sm\"\n :icon=\"show ? 'i-lucide-eye-off' : 'i-lucide-eye'\"\n aria-label=\"show ? 'Hide password' : 'Show password'\"\n :aria-pressed=\"show\"\n aria-controls=\"password\"\n @click=\"show = !show\"\n />\n \u003C/template>\n \u003C/UInput>\n\u003C/template>\n\n\u003Cscript setup lang=\"ts\">\nconst show = ref(false)\nconst password = ref('password')\n\u003C/script>\n```",[2929,2930],{"name":2866,"color":2867},{"name":2869,"color":2870},2806,"input: add toggle password button automatically for type password","2024-12-02T17:21:42Z","https://github.com/nuxt/ui/issues/2806",0.69525355,{"description":2937,"labels":2938,"number":2948,"owner":2875,"repository":2876,"state":2906,"title":2949,"updated_at":2950,"url":2951,"score":2952},"### Environment\n\nNode 22\nNuxt 4\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0 alpha 10\n\n### Reproduction\n\n1. create a modal and a slideover using useModal and useSlideover\n2. create a button **(first button**) that opens the modal with useModal()\n3. create one as well **(second button**) INSIDE! the slideover that opens the same modal with useModal()\n\n### Description\n\nNow open the modal outside the slideover with the **first button**. Thats set an index I suppose.\nBut now if you open the slideover and click the **second button** which opens the same modal, it appears behind the slideover.\n\nBut if you reload the page, open the slideover first and then press the second button without ever pressing the first button to open the modal it appears infront.\n\n### Additional context\n\n\n\n\n\n### Logs\n\n```shell-script\n\n```",[2939,2940,2943,2944,2945],{"name":2902,"color":2903},{"name":2941,"color":2942},"needs reproduction","CB47CF",{"name":2869,"color":2870},{"name":2872,"color":2873},{"name":2946,"color":2947},"closed-by-bot","ededed",3079,"Modal and slideover z-index bug","2025-03-25T02:04:49Z","https://github.com/nuxt/ui/issues/3079",0.69946015,{"description":2954,"labels":2955,"number":2958,"owner":2875,"repository":2876,"state":2906,"title":2959,"updated_at":2960,"url":2961,"score":2962},"### Description\n\nIn v3, we seem to have lost any focus indication on Buttons. This looks intentional as I see `focus:outline-hidden` on the base. For a11y and good keyboard navigation, it's best practice to have a visual indication of focus: https://www.w3.org/WAI/ARIA/apg/practices/keyboard-interface/#discernibleandpredictablekeyboardfocus\n\nIt seems we've taken a step backward from v2 in this regard. Was this intentional? Is the intent for users to add their own `focus-visible:*` classes via app config?",[2956,2957],{"name":2915,"color":2916},{"name":2869,"color":2870},3658,"Button Focus Indication","2025-03-24T09:50:12Z","https://github.com/nuxt/ui/issues/3658",0.7099639,{"description":2964,"labels":2965,"number":2970,"owner":2875,"repository":2876,"state":2906,"title":2971,"updated_at":2972,"url":2973,"score":2974},"### Environment\n\nnuxt@3.13.2\r\n@nuxt/ui@2.18.4\n\n### Version\n\nv2.18.4\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/modal#usage\n\n### Description\n\nThe modal enter transtition isn't working at all, it just appears immediately. Check it out in the [documentation](https://ui.nuxt.com/components/modal#usage).\n\n### Additional context\n\nhttps://github.com/user-attachments/assets/3897833a-6245-4ddf-8db8-2c1dfd117e0b\r\n\n\n### Logs\n\n_No response_",[2966,2967],{"name":2902,"color":2903},{"name":2968,"color":2969},"duplicate","cfd3d7",2211,"Modal enter transition not working","2024-09-17T08:47:43Z","https://github.com/nuxt/ui/issues/2211",0.7118644,{"description":2976,"labels":2977,"number":2980,"owner":2875,"repository":2981,"state":2906,"title":2982,"updated_at":2983,"url":2984,"score":2985},"http://localhost:3000/integrations?version=2.x\n\n",[2978],{"name":2902,"color":2979},"ff281a",549,"nuxt.com","[Integrations] Version selector is not valid on refresh with query param","2023-02-15T12:32:31Z","https://github.com/nuxt/nuxt.com/issues/549",0.7127539,{"description":2987,"labels":2988,"number":2980,"owner":2875,"repository":2995,"state":2906,"title":2996,"updated_at":2997,"url":2998,"score":2985},"My dev dependencies: \r\n```\r\n{\r\n \"@nuxt/devtools\": \"^0.5.5\",\r\n \"@nuxtjs/tailwindcss\": \"^6.4.1\",\r\n \"@vitest/coverage-c8\": \"^0.31.3\",\r\n \"nuxt\": \"^3.5.2\",\r\n \"nuxt-vitest\": \"0.8.2\",\r\n \"tailwindcss\": \"^3.3.2\",\r\n \"vitest\": \"^0.31.3\"\r\n }\r\n```\r\n\r\nThe app is building fine, but trying to start Vitest is causing the following error:\r\n`ERROR Only URLs with a scheme in: file and data are supported by the default ESM loader. On Windows, absolute paths must be valid file:// URLs. Received protocol 'c:'`\r\n\r\nIt seems to be breaking down on `const { startVitest } = await import(await resolvePath(\"vitest/node\"));` in `module.mjs`\r\n\r\nIs anyone else experiencing this issue with the latest version of Nuxt or is it just me?",[2989,2992],{"name":2990,"color":2991},"vitest-environment","b60205",{"name":2993,"color":2994},"windows","6FA283","test-utils","Dynamic module import seems to be causing error","2023-12-02T00:17:10Z","https://github.com/nuxt/test-utils/issues/549",["Reactive",3000],{},["Set"],["ShallowReactive",3003],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fkRrzDCkLBPV_8kb31mIAReKYzOdQRrpyAT037-I2qVk":-1},"/nuxt/nuxt.com/412"]