\n \u003C/template>\n \u003CUButton\n label=\"Open\"\n color=\"neutral\"\n variant=\"subtle\"\n trailing-icon=\"i-lucide-chevron-down\"\n block\n />\n \u003C/UCollapsible>\n\n### Additional context\n\n_No response_",[3032,3035,3038],{"name":3033,"color":3034},"enhancement","a2eeef",{"name":3036,"color":3037},"v3","49DCB8",{"name":3039,"color":3040},"triage","ffffff",4146,"ui","Can we add a reverse prop for collapsible.","2025-05-13T21:49:55Z","https://github.com/nuxt/ui/issues/4146",0.7527561,{"description":3048,"labels":3049,"number":3053,"owner":3023,"repository":3042,"state":3024,"title":3054,"updated_at":3055,"url":3056,"score":3057},"### Description\n\nI propose the addition of a UTheme component which would allow scoped theming of components to reduce repeated styling that's error prone when refactoring.\n\n## Example\nThe Dashboard template has a bunch of forms that have horizontal form fields (label left, input right).\n\nBefore:\n```html\n\u003CUForm ...>\n \u003CUFormField ... class=\"flex max-sm:flex-col justify-between items-center gap-4\">\n ...\n \u003CUFormField>\n \u003CUFormField ... class=\"flex max-sm:flex-col justify-between items-center gap-4\">\n ...\n \u003CUFormField>\n\u003CUForm/>\n```\n\nAfter:\n```html\n\u003C!-- `ui` prop is the same as `app.config.ts` theming config\n\u003CUTheme :ui=\"{\n formField: {\n\t slots: {\n\t root: \"flex max-sm:flex-col justify-between items-center gap-4\",\n\t},\n },\n}\">\n \u003CUForm ...>\n \u003CUFormField ...>\n ...\n \u003CUFormField>\n \u003CUFormField ...>\n ...\n \u003CUFormField>\n \u003CUForm/>\n\u003C/UTheme>\n```\n\n## Benefits\n- Easily componentized. I could create a `AppForm` component which contains the `UTheme` usage with a slot, so now its 1 line to get the exact theming that I want. This makes consistency across the app really easy.\n- Nestable - If implemented with provide/inject, you could have an infinite number of UTheme's nested and it would take the latest one\n\n## Implementation\nI'd tentatively be willing to implement this. My approach would be:\n- Create `UTheme`, it should have a `ui` and `uiPro` prop, each of which take the same type as the `app.config.ts`\n- `provide()` those props\n- `inject()` those props into each component and merge with passed in `ui` field.\n- Theme priority order should be:\n 1. `ui` prop passed to component\n 2. `ui` prop coming from UTheme component\n 3. `ui` config coming from `app.config.ts`\n\n### Additional context\n\n_No response_",[3050,3051,3052],{"name":3033,"color":3034},{"name":3036,"color":3037},{"name":3039,"color":3040},4250,"UTheme component","2025-05-28T22:24:36Z","https://github.com/nuxt/ui/issues/4250",0.7800318,{"description":3059,"labels":3060,"number":3065,"owner":3023,"repository":3023,"state":3024,"title":3066,"updated_at":3067,"url":3068,"score":3069},"It should be nice to have a go back button `window.history.back()` here :\r\nhttps://github.com/nuxt/assets/blob/aa803dceebb99a83b65401bcf90c259bc0d63a62/packages/templates/templates/error-404/index.html#LL71C9-L71C10",[3061,3062],{"name":3020,"color":3021},{"name":3063,"color":3064},"ui-templates","bfd4f2",27084,"Go back","2024-06-30T11:09:18Z","https://github.com/nuxt/nuxt/issues/27084",0.789879,{"description":3071,"labels":3072,"number":3076,"owner":3023,"repository":3077,"state":3024,"title":3078,"updated_at":3079,"url":3080,"score":3081},"Whenever I reload my page the font flickers",[3073],{"name":3074,"color":3075},"bug","d73a4a",181,"fonts","Loading fonts causes flickering in dev mode","2025-03-23T22:52:32Z","https://github.com/nuxt/fonts/issues/181",0.7907641,{"description":3083,"labels":3084,"number":3088,"owner":3023,"repository":3042,"state":3089,"title":3090,"updated_at":3091,"url":3092,"score":3093},"### Description\n\nsimilar github.com home page\r\n\r\n\n\n### Additional context\n\n_No response_",[3085],{"name":3086,"color":3087},"feature","A27AF6",814,"closed","I would like to ask, have you considered making a new component: timeline?","2025-05-30T13:27:12Z","https://github.com/nuxt/ui/issues/814",0.7638288,{"description":3095,"labels":3096,"number":3103,"owner":3023,"repository":3042,"state":3089,"title":3104,"updated_at":3105,"url":3106,"score":3107},"### Description\n\nHi Team,\r\n\r\nI hope you're doing well.\r\n\r\nI have a feature request for the pagination component. I'm using pagination for a series, and some series don't start at season 1. For example, some might start at season 4.\r\n\r\nIt would be incredibly useful to have a min prop that allows specifying a minimum page so that everything below this minimum is automatically disabled or hidden.\r\n\r\nHere's an example of how it might be implemented:\r\n\r\n```\r\n\u003CUPagination\r\n v-model=\"selectedSeason\"\r\n :min=\"selectedSeason \u003C seasonRange.minSeason\"\r\n :max=\"5\"\r\n size=\"sm\"\r\n :page-count=\"1\"\r\n :total=\"seasonRange.maxSeason\"\r\n :active-button=\"{ variant: 'outline' }\"\r\n :ui=\"{ rounded: 'first-of-type:rounded-s-md last-of-type:rounded-e-md' }\"\r\n show-last\r\n show-first\r\n>\r\n\u003C/UPagination>\r\n```\r\n\n\n### Additional context\n\nIn this example, :min=\"selectedSeason \u003C seasonRange.minSeason\" would ensure that seasons below the minimum are disabled or hidden.\r\n\r\nThank you for considering this feature request. It would greatly enhance the usability of the pagination component for series with non-sequential seasons.",[3097,3098,3101],{"name":3033,"color":3034},{"name":3099,"color":3100},"closed-by-bot","ededed",{"name":3102,"color":3100},"stale",1804,"Feature Request: Allow min-page Property in Pagination Component","2025-06-19T02:12:27Z","https://github.com/nuxt/ui/issues/1804",0.77074355,{"description":3109,"labels":3110,"number":3113,"owner":3023,"repository":3042,"state":3089,"title":3114,"updated_at":3115,"url":3116,"score":3117},"### For what version of Nuxt UI are you suggesting this?\n\nv3-alpha\n\n### Description\n\nI was browsing through the v3 carousel docs at https://ui.nuxt.com/components/carousel#props, to see whether the v3 version will have callback events for onPrev and onNext, but didn't find it.\n\nIs this something that would be considered to implement?\n\nAlternatively, the ability to bind to the active item in the carousel, could also work.\n\nWe would use it to display an info text next to the image, and change it depending on which image is active in the carousel.\n\nIf this is something that is already possible, then please let me know how :)",[3111,3112],{"name":3033,"color":3034},{"name":3036,"color":3037},2475,"[v3] `Carousel` feature request: callback methods onPrev & onNext","2024-11-07T14:11:43Z","https://github.com/nuxt/ui/issues/2475",0.77435035,{"description":3119,"labels":3120,"number":3128,"owner":3023,"repository":3023,"state":3089,"title":3129,"updated_at":3130,"url":3131,"score":3132},"### Describe the feature\n\nMaybe you can get us information about previous route? Just like we do it in nuxt 2 by accessing in this.$nuxt.context.from . Im try to found information about that last few hours, but I didn't find anything useful.\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://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3121,3124,3127],{"name":3122,"color":3123},"3.x","29bc7f",{"name":3125,"color":3126},"workaround available","11376d",{"name":3020,"color":3021},27416,"Previous route info","2024-06-03T09:11:04Z","https://github.com/nuxt/nuxt/issues/27416",0.77714515,{"description":3134,"labels":3135,"number":3139,"owner":3023,"repository":3042,"state":3089,"title":3140,"updated_at":3141,"url":3142,"score":3143},"### Description\n\nThis is a re-opening of #1484 but for v3. It seems in the transition from v2 to v3, giving the indicators (now \"dots\") ARIA \"tab\" roles was lost. While I did mention it in my original issue, I don't believe my original PR accounted for when multiple items would be displayed at the same time. Perhaps the changes for v3 can take that into account.\n\n### Additional context\n\n_No response_",[3136,3137,3138],{"name":3033,"color":3034},{"name":3036,"color":3037},{"name":3039,"color":3040},4494,"Carousel component could be made more accessible (v3).","2025-07-10T12:18:41Z","https://github.com/nuxt/ui/issues/4494",0.7781342,["Reactive",3145],{},["Set"],["ShallowReactive",3148],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fo7vssePUerNRQZW_jlGs1xMU3JSXeaM_IUhkXOfIQk8":-1},"/nuxt/ui/4299"]