\n\n\n## Summary\nI would like to request the addition of a `header` slot to the Accordion component in Nuxt UI. This would provide more flexibility for customizing the accordion header content beyond the current available slots.\n\n## Current Behavior\nThe Accordion component currently supports the following slots:\n- `body`\n- `content` \n- `default`\n- `leading`\n- `trailing`\n\n## Proposed Enhancement\nAdd a new `header` slot that allows developers to completely customize the header content of each accordion item.\n\n## Use Case\nI need to display additional information in the accordion title when it's in a collapsed state. The current slots (`leading`, `trailing`) provide some customization, but a dedicated `header` slot would allow for more complex layouts and better control over the entire header area.\n\nFor example, I want to show:\n- Custom formatted titles\n- Additional metadata or status indicators\n- Complex layouts that go beyond simple leading/trailing elements\n\n## Implementation Suggestion\nMy idea is to position the `header` slot **below the existing header area** as a supplementary display zone. This would:\n- Preserve the current header functionality (title, leading/trailing slots, toggle button)\n- Add an additional customizable area underneath for extra information\n- Maintain visual hierarchy while providing more space for content\n\n## Expected API\n```vue\n\u003CUAccordion :items=\"items\">\n\u003Ctemplate #header=\"{ item, index, open }\">\n \u003Cdiv class=\"supplementary-header-info\">\n \u003Cspan class=\"status-badge\">{{ item.status }}\u003C/span>\n \u003Cp class=\"description\">{{ item.summary }}\u003C/p>\n \u003C/div>\n\u003C/template>\n\u003C/UAccordion>\n```\n\n**Visual Layout:**\n```\n┌─────────────────────────────────────┐\n│ [Leading] Title Text [Trailing] ▼│ ← Existing header\n├─────────────────────────────────────┤\n│ Custom Header Slot Content │ ← New header slot\n└─────────────────────────────────────┘\n```\n\n## Benefits\n1. **Enhanced Flexibility**: Developers can create more sophisticated header layouts\n2. **Better UX**: Ability to show contextual information when accordion items are collapsed\n3. **Consistency**: Aligns with the existing slot-based architecture of other Nuxt UI components\n4. **Backward Compatibility**: Would not break existing implementations\n5. **Non-intrusive**: Positioned below existing header, maintaining current functionality\n\n## Additional Context\nThis feature would be particularly useful for:\n- Dashboard interfaces where accordion headers need to show status information\n- Form sections that display validation states in headers\n- Data tables collapsed into accordion format with summary information\n- Preview content or metadata display without expanding the full accordion\n\nThank you for considering this enhancement!\n\n### Additional context\n\n_No response_",[3137,3140,3143],{"name":3138,"color":3139},"enhancement","a2eeef",{"name":3141,"color":3142},"v3","49DCB8",{"name":3144,"color":3145},"triage","ffffff",4782,"nuxt","ui","open","Feature Request: Add Header Slot to Accordion Component","2025-08-21T18:07:41Z","https://github.com/nuxt/ui/issues/4782",0.70243496,{"description":3155,"labels":3156,"number":3163,"owner":3147,"repository":3147,"state":3164,"title":3165,"updated_at":3166,"url":3167,"score":3168},"### Environment\n\nNuxt 3.0.0-rc.11\n\n### Reproduction\n\nStackBlitz: https://stackblitz.com/edit/nuxt3-layout-slot-bug\n\n### Describe the bug\n\nLayout slots not working with default layout, generate error (see reproduction):\r\n\r\n```\r\nError: Codegen node is missing for element/if/for node. Apply appropriate transforms first.\r\n```\r\n\r\nNote the use of `app.vue`.\r\n\r\nExplicitly using `\u003CNuxtLayout>` with `layout: false` in page meta works but leads to full re-render of the layout and kinda defies the purpose of a default layout.\r\n\r\nNot sure if I'm doing something wrong with the setup, but following the docs, the code in the repro should work. Also, best in terms of DX IMO.\n\n### Additional context\n\nThis is a typical use case where you for instance have a nav and want to add additional items via a slot on specific pages.\n\n### Logs\n\n_No response_",[3157,3160],{"name":3158,"color":3159},"3.x","29bc7f",{"name":3161,"color":3162},"pending triage","E99695",15158,"closed","Layout slots not working in default layout","2023-09-26T14:37:01Z","https://github.com/nuxt/nuxt/issues/15158",0.6970522,{"description":3170,"labels":3171,"number":3179,"owner":3147,"repository":3147,"state":3164,"title":3180,"updated_at":3181,"url":3182,"score":3183},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.9.3\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: devtools, experimental\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-issues-25423\r\n\r\n### Describe the bug\r\n\r\nUsing nested slots in a server components + `nuxt-client` breaks:\r\n\r\nExample\r\n\r\n```vue\r\n\u003C!-- ServerComp.vue -->\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CAppButton nuxt-client>\r\n \u003Cslot />\r\n \u003C/AppButton>\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\n```vue\r\n\u003C!-- App.vue -->\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CServerComp>\r\n Some slot content here\r\n \u003C/ServerComp>\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3172,3173,3176],{"name":3158,"color":3159},{"name":3174,"color":3175},"🔨 p3-minor","FBCA04",{"name":3177,"color":3178},"server components","839413",25423,"Respect named slots in server components","2024-03-06T15:26:20Z","https://github.com/nuxt/nuxt/issues/25423",0.70008737,{"description":3185,"labels":3186,"number":3189,"owner":3147,"repository":3147,"state":3164,"title":3190,"updated_at":3191,"url":3192,"score":3193},"### Environment\n\n------------------------------\r\n- Operating System: `Windows_NT`\r\n- Node Version: `v16.16.0`\r\n- Nuxt Version: `3.1.2`\r\n- Nitro Version: `2.1.1`\r\n- Package Manager: `yarn@1.22.17`\r\n- Builder: `vite`\r\n- User Config: `modules`, `vuestic`\r\n- Runtime Modules: `@vuestic/nuxt@1.0.9`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\n1. create component as below\r\n\r\nBtn.vue\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Cslot name=\"header\">\u003C/slot>\r\n \u003Cslot>\u003C/slot>\r\n \u003Cslot name=\"slot1\">\u003C/slot>\r\n \u003Cslot name=\"slot2\">\u003C/slot>\r\n \u003Cslot name=\"footer\">\u003C/slot>\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript setup>\u003C/script>\r\n\r\n\u003Cstyle lang=\"scss\" scoped>\u003C/style>\r\n```\r\n\r\n2. build project `yarn build`\r\n3. run `yarn preview`\r\n4. inspect DOM\r\n\n\n### Describe the bug\n\nthis is resulting html of built project\r\n\r\n```html\r\n\u003Cdiv id=\"__nuxt\">\r\n \u003Cdiv>\r\n \u003C!--[-->\r\n \u003C!--]-->\r\n \u003C!--[-->\r\n im a button\r\n \u003C!--]-->\r\n \u003C!--[-->\r\n \u003C!--]-->\r\n \u003C!--[-->\r\n \u003C!--]-->\r\n \u003C!--[-->\r\n \u003C!--]-->\r\n \u003C/div>\r\n\u003C/div>\r\n```\r\n\r\nIs it possible to get rid of generated comments in place of empty slots?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3187,3188],{"name":3158,"color":3159},{"name":3161,"color":3162},18754,"component slots end up as comments","2023-02-05T13:45:07Z","https://github.com/nuxt/nuxt/issues/18754",0.70694315,{"description":3195,"labels":3196,"number":3203,"owner":3147,"repository":3147,"state":3164,"title":3204,"updated_at":3205,"url":3206,"score":3207},"\u003C!-- 💚 Thanks for your time to make Nuxt better with your feedbacks 💚\r\n\r\n**IMPORTANT** Before reporting a bug:\r\n\r\n- Please make sure that you have read through Nuxt documentation: https://nuxtjs.org\r\n- If issue is related to a module please create the issue in corresponding repository\r\n- Ensure using latest version of nuxt dependencies using `yarn upgrade nuxt` or `npm upgrade nuxt`\r\n\r\n👍 A properly detailed bug report can save a LOT of time and help fixing issues as soon as possible.\r\n-->\r\n\r\n### Versions\r\n\r\n- nuxt: 2.14.12\r\n- node: 14.15.0\r\n\r\n### Reproduction\r\n\r\n\u003C!--\r\nLink to a minimal test case based on one of:\r\n- A fork of https://template.nuxtjs.org\r\n- A GitHub repository that can reproduce the bug\r\nWithout a reproduction, it is so hard to address problem :(\r\n-->\r\n\r\n\u003Cdetails open>\r\n\u003Csummary>Additional Details\u003C/summary>\r\n\u003Cbr>\r\n\u003C!-- Attaching `nuxt.config`, dependencies, logs or code snippets would help to find the issue -->\r\n\u003C/details>\r\n\r\n### Steps to reproduce\r\n\r\n1. Create Vue.js component with a named slot of your choice\r\n2. Use created component and provide the content for the slot (wrap everything in `\u003Cclient-only>` tag); example below:\r\n```\r\n\u003CStepper\r\n :steps=\"[$t('steps.one'), $t('steps.two'), $t('steps.three')]\"\r\n>\r\n \u003Ctemplate slot=\"step-1\">\r\n \u003Cdiv>\r\n \u003Cclient-only placeholder=\"Loading...\">\r\n \u003C!-- Neither a span tag nor v-calendar plugin works (tested one by one) -->\r\n \u003Cspan>Test\u003C/span>\r\n \u003Cdiv>\r\n \u003Cv-date-picker\r\n v-model=\"dates\"\r\n is-expanded\r\n trim-weeks\r\n />\r\n \u003C/div>\r\n \u003C/client-only>\r\n \u003C/div>\r\n \u003C/template>\r\n\u003C/Stepper>\r\n```\r\nThe placeholder remains with no content replaced as shown below:\r\n\r\n\r\n### What is Expected?\r\nContent inside `\u003Cclient-only>` tag should get rendered instead of getting stuck on the placeholder (or blank state if placeholder not provided).\r\n\r\n### What is actually happening?\r\n`\u003Cclient-only>` tag does not render its content when the tag is placed inside a component slot, as shown in the provided example. It does render when placed outside of the slot.",[3197,3199,3200],{"name":3198,"color":3145},"stale",{"name":3161,"color":3162},{"name":3201,"color":3202},"2.x","d4c5f9",8579,"Client-only content doesn't render in component's slot","2023-01-22T15:38:40Z","https://github.com/nuxt/nuxt/issues/8579",0.70742637,{"description":3209,"labels":3210,"number":3216,"owner":3147,"repository":3147,"state":3164,"title":3217,"updated_at":3218,"url":3219,"score":3220},"### Environment\n\n```\nWorking directory: /home/projects/gqairmgblw.github 17:37:59\nNuxt project info: 17:37:59\n\n------------------------------\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.13.2\n- CLI Version: 3.14.0\n- Nitro Version: 2.9.7\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n```\n\n### Reproduction\n\nNuxt 3 minimal reproduction (3.13.2):\nhttps://stackblitz.com/edit/github-tt5jnt-dpu8vc\n\nLast working nuxt version 3.9.1:\nhttps://stackblitz.com/edit/github-tt5jnt-hmnuhm?file=package.json\n\nFirst broken nuxt version 3.9.2:\nhttps://stackblitz.com/edit/github-tt5jnt-h36nnu?file=package.json\n\n\n### Describe the bug\n\nBarebone Nuxt 3 reproduction with `ssr: true` and a `.server` component that has an unused `\u003Cslot />` This has been working up until the release of 3.9.2: https://github.com/nuxt/nuxt/releases/tag/v3.9.2\n\nSomeServerComponentWithSlot.server.vue:\n```html\n\u003Ctemplate>\n \u003Cdiv>\n \u003Ch1>HELLO FROM SERVER\u003C/h1>\n \u003Cslot />\n \u003C/div>\n\u003C/template>\n```\n\napp.vue:\n```\n\u003Ctemplate>\n \u003Cdiv>\n \u003CSomeServerComponentWithSlot>\n \u003Cp>Hi from the slot!\u003C/p>\n \u003C/SomeServerComponentWithSlot>\n \u003C/div>\n\u003C/template>\n```\n\n```\n❯ npm run build\n\n> build\n> nuxt build\n\nNuxt 3.13.2 with Nitro 2.9.7 17:39:06\nℹ Compiled plugins/server.mjs in 724.52ms 17:39:15\nℹ Compiled plugins/client.mjs in 841.95ms 17:39:15\nℹ Compiled types/plugins.d.ts in 843.21ms 17:39:15\nℹ Building client... 17:39:18\nℹ vite v5.4.8 building for production... 17:39:18\nℹ ✓ 117 modules transformed. 17:39:22\nℹ .nuxt/dist/client/manifest.json 1.20 kB │ gzip: 0.31 kB 17:39:24\nℹ .nuxt/dist/client/_nuxt/error-500.B11Ibp8J.css 1.88 kB │ gzip: 0.72 kB 17:39:24\nℹ .nuxt/dist/client/_nuxt/error-404.ygbHJO5Q.css 3.56 kB │ gzip: 1.11 kB 17:39:24\nℹ .nuxt/dist/client/_nuxt/C_GX9_hV.js 0.38 kB │ gzip: 0.26 kB 17:39:24\nℹ .nuxt/dist/client/_nuxt/B8I165mB.js 3.41 kB │ gzip: 1.54 kB 17:39:24\nℹ .nuxt/dist/client/_nuxt/C5XsKPLf.js 9.27 kB │ gzip: 3.73 kB 17:39:24\nℹ .nuxt/dist/client/_nuxt/BdW2tdLc.js 141.17 kB │ gzip: 53.67 kB 17:39:24\nℹ ✓ built in 5.74s 17:39:24\n✔ Client built in 5779ms 17:39:24\nℹ Building server... 17:39:24\nℹ vite v5.4.8 building SSR bundle for production... 17:39:24\nℹ ✓ 54 modules transformed. 17:39:25\n\n ERROR x Build failed in 1.72s 17:39:25\n\n\n**[17:39:25] ERROR Nuxt Build Error: [vite:load-fallback] Could not load /home/projects/gqairmgblw.github/.nuxt/components-chunk (imported by node_modules/nuxt/dist/app/components/nuxt-teleport-island-component.js): ENOENT: no such file or directory, open '/home/projects/gqairmgblw.github/.nuxt/components-chunk'\n\n ENOENT: no such file or directory, open '.nuxt/components-chunk'**\n\n\n~/projects/gqairmgblw.github 21s\n```\n\n### Additional context\n\nIf works fine if the server component doesn't have a slot. It also doesn't matter if you provide slot content or not. The pure existence of the slot results in a Nuxt Build Error.\n\n### Logs\n\n_No response_",[3211,3212,3213],{"name":3161,"color":3162},{"name":3177,"color":3178},{"name":3214,"color":3215},"possible regression","B90A42",29354,"Server Component (.server) and NuxtIsland with Slot results in Nuxt Build Error (SSR) - broken since nuxt@3.9.2","2025-01-25T15:38:57Z","https://github.com/nuxt/nuxt/issues/29354",0.70885533,{"description":3222,"labels":3223,"number":3226,"owner":3147,"repository":3148,"state":3164,"title":3227,"updated_at":3228,"url":3229,"score":3230},"### Environment\n\n- Operating System: Darwin\n- Node Version: v23.11.0\n- Nuxt Version: 4.0.0\n- CLI Version: 3.27.0\n- Nitro Version: 2.12.0\n- Package Manager: pnpm@10.10.0\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, css, colorMode, fonts, icon\n- Runtime Modules: @nuxt/ui-pro@3.1.3, @nuxt/eslint@1.4.1, @vueuse/nuxt@13.5.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.1.3\n\n### Reproduction\n\n- \n\n### Description\n\n Description\n\n The UChatMessage component has two issues with the parts prop:\n 1. The parts prop appears to be completely non-functional - it doesn't render any parts regardless of configuration\n 2. The content prop is required even when using parts, but providing both causes conflicts\n\n Expected Behavior\n\n 1. When parts prop is provided, it should render structured message content (text, reasoning, tool invocations, etc.) as documented\n 2. The content prop should be optional when parts is provided, or at minimum not interfere with parts rendering\n\n Actual Behavior\n\n 1. The parts prop doesn't render anything - no text parts, reasoning parts, or tool invocation parts appear\n 2. Removing the content prop causes Vue warnings about missing required prop and the page doesn't render at all\n 3. When both content and parts are provided, only the content is shown\n\n Reproduction Steps\n\n 1. Test parts alone (breaks completely):\n \u003CUChatMessage\n :parts=\"[\n { type: 'text', text: 'Main message' },\n { type: 'reasoning', reasoning: 'This is the reasoning' }\n ]\"\n />\n 1. Result: Vue warning \"Missing required prop: 'content'\" and nothing renders\n 2. Test parts with content (parts ignored):\n \u003CUChatMessage\n content=\"Main message\"\n :parts=\"[\n { type: 'text', text: 'Main message' },\n { type: 'reasoning', reasoning: 'This is the reasoning' }\n ]\"\n />\n 2. Result: Only \"Main message\" displays, reasoning part is completely ignored\n 3. Test different part types:\n \u003CUChatMessage\n content=\"fallback\"\n :parts=\"[\n { type: 'text', text: 'Text part' },\n { type: 'tool-invocation', toolInvocation: { /* tool data */ } }\n ]\"\n />\n 3. Result: Only \"fallback\" content shows, no parts render\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3224],{"name":3225,"color":3142},"v4",4685,"UI Pro: ChatMessage: parts prop not working and content prop is required even when using parts","2025-08-12T08:32:49Z","https://github.com/nuxt/ui/issues/4685",0.70885575,{"description":3232,"labels":3233,"number":3238,"owner":3147,"repository":3148,"state":3164,"title":3239,"updated_at":3240,"url":3241,"score":3242},"\u003Cdetails>\n \u003Csummary>Environment\u003C/summary>\n\n------------------------------\n- Operating System: Linux\n- Node Version: v22.16.0\n- Nuxt Version: 3.17.4\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: npm@11.4.1\n- Builder: -\n- User Config: modules, ssr, devtools, app, css, ui, runtimeConfig, alias, build, devServer, watch, future, experimental, compatibilityDate, nitro, vite, eslint, heyApi, i18n, icon, svgIconSprite\n- Runtime Modules: @nuxt/ui@3.1.2, @nuxt/test-utils/module@3.19.0, @nuxt/eslint@1.4.1, @pinia/nuxt@0.11.0, @vueuse/nuxt@13.2.0, @hey-api/nuxt@0.1.6, @nuxtjs/i18n@9.5.4, nuxt-svg-icon-sprite@2.0.0\n- Build Modules: -\n------------------------------\n\u003C/details>\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.2\n\n### Reproduction\n\nhttps://www.npmjs.com/package/@nuxt/ui?activeTab=code - `interface ModalSlots`\n\n### Description\n\nGreetings, thank you very much for the work you have done!\n\nUsing the example of the `UModal` component, you can see that props in scoped slots, such as `#footer=“{ close }”`, is untyped \n\u003Cdetails>\n \u003Csummary>Example\u003C/summary>\n\n \n\u003C/details>\n\nin the bundle package it can be seen that there are indeed no valid types of props in `ModalSlots` - https://www.npmjs.com/package/@nuxt/ui?activeTab=code `interface ModalSlots`, although they are present in the source files - https://github.com/nuxt/ui/blob/v3/src/runtime/components/Modal.vue#L70\n\n\nAs I understand it, it is not only `UModal`, but all components with scoped slots.",[3234,3237],{"name":3235,"color":3236},"bug","d73a4a",{"name":3141,"color":3142},4260,"Scoped slots are not typed","2025-06-02T09:08:41Z","https://github.com/nuxt/ui/issues/4260",0.7093344,{"description":3244,"labels":3245,"number":3249,"owner":3147,"repository":3147,"state":3164,"title":3250,"updated_at":3251,"url":3252,"score":3253},"### Environment\n\nnuxt rc 13\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-g7nvjf?file=app.vue\n\n### Describe the bug\n\nHi :wave: this is a very small issue, currently it seems that `ClientOnly` is trying to make its default slot inherit its attributes. It triggers a warn message in the console since the default slot is rendered using a Fragment.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3246,3247,3248],{"name":3158,"color":3159},{"name":3235,"color":3236},{"name":3174,"color":3175},15444,"ClientOnly attrs are passed to the default slot","2023-01-19T17:50:34Z","https://github.com/nuxt/nuxt/issues/15444",0.70968246,{"description":3255,"labels":3256,"number":3258,"owner":3147,"repository":3147,"state":3164,"title":3259,"updated_at":3260,"url":3261,"score":3262},"### Environment\r\n\r\n- Operating System: Windows_NT\r\n- Node Version: v20.11.0\r\n- Nuxt Version: 3.12.4\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: yarn@1.22.22\r\n- Builder: -\r\n- User Config: modules, colorMode, devtools, srcDir,\r\n css, compatibilityDate\r\n- Runtime Modules: @nuxt/ui@2.18.4, @nuxtjs/google-fonts@3.2.0, @nuxt/eslint@0.4.0, @nuxt/image@1.7.0\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\nThis is my MembersDetailInformation component\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv class=\"flex flex-col gap-4\">\r\n \u003Cdiv>\r\n \u003Cspan class=\"text-lg font-bold\">About this member\u003C/span>\r\n \u003Cul>\r\n \u003Cli v-for=\"item in about\" :key=\"item\">{{ item }}\u003C/li>\r\n \u003C/ul>\r\n \u003C/div>\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript setup lang=\"ts\">\r\nimport type { MembersDetailInformationProps } from '~/types/members'\r\n\r\ndefineProps\u003CMembersDetailInformationProps>()\r\n\u003C/script>\r\n```\r\n\r\nThis is the props of above component\r\n```ts\r\nexport type MembersDetailInformationProps = {\r\n about: string[]\r\n activites: string[]\r\n quote: string\r\n}\r\n```\r\n\r\nAnd data for above component\r\n```ts\r\n{\r\n about: [\r\n 'Lorem ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum',\r\n 'Lorem ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum',\r\n 'Lorem ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum'\r\n ],\r\n activites: [\r\n 'Lorem ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum',\r\n 'Lorem ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum',\r\n 'Lorem ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum'\r\n ],\r\n quote: 'Lorem ipsum ipsum ipsum ipsum ipsum ipsum ipsum ipsum',\r\n}\r\n```\r\n\r\n### Describe the bug\r\n\r\nI don't know why the bullet points of the ul tag disappeared.\r\n\r\n\r\nI think my issue is very easy to deal with, but I still cannot find the solution :((((\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3257],{"name":3161,"color":3162},28636,"Why are the bullet points hidden?","2024-08-21T20:00:54Z","https://github.com/nuxt/nuxt/issues/28636",0.7103911,["Reactive",3264],{},["Set"],["ShallowReactive",3267],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fGxerqimdpxKl30UYRLbQldoUqKORaHBgtBNXo1RNFKc":-1},"/nuxt/ui/2057"]