nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

table inside of an expand macro

Tina-Louise Allaire

I am using the legacy version and I used to be able to put a table inside of an expand macro but not it not supported. Does anyone have a workaround?

Accepted answers

Germán Morales

Hi @Tina-Louise Allaire ,

This is supported in the current Confluence Cloud editor. Insert an Expand element first, click inside its body, then insert a normal Confluence table.

If the page was originally created with the legacy editor and the content is now inside a Legacy content block, don’t try to rebuild the structure inside that block. Create a new Expand in the normal Cloud editor area and recreate the table inside it.

Atlassian documents the current behavior here:

Insert the Expand macro:
https://support.atlassian.com/confluence-cloud/docs/insert-the-expand-macro/

Charts and connected data:
https://support.atlassian.com/confluence-cloud/docs/charts-and-connected-data/

Legacy editor content in the Cloud editor:
https://support.atlassian.com/confluence-cloud/docs/legacy-editor-content-in-the-cloud-editor/

All comments

Germán Morales

Hi @Tina-Louise Allaire ,

This is supported in the current Confluence Cloud editor. Insert an Expand element first, click inside its body, then insert a normal Confluence table.

Atlassian documents the current behavior here:

Insert the Expand macro:
https://support.atlassian.com/confluence-cloud/docs/insert-the-expand-macro/

Charts and connected data:
https://support.atlassian.com/confluence-cloud/docs/charts-and-connected-data/

Legacy editor content in the Cloud editor:
https://support.atlassian.com/confluence-cloud/docs/legacy-editor-content-in-the-cloud-editor/

Kris Klima _K15t_

Hi @Tina-Louise Allaire

As @Germán Morales writes, it's best to step outside the legacy content. Based on the anecdotal evidence from this community fora, legacy content can cause issues down the line.

As with any migration, if a wholesale conversion (or sanitization) of the imported/migrated content is not possible, I recommend converting any page that needs an update in your normal line of work.

In your case, if you need to add content (a table in the expand macro), I'd rebuild the entire page.

This is how it looks in the modern editor

Josh

In the current Confluence Cloud editor, nesting a full table inside Expand is restricted compared with legacy — a lot of people hit the same wall after migrating pages.

Workarounds that still work:

Put the table immediately under the Expand (outside it) and use Expand only for a short summary, or
Use Expand → Panel/Info with a simpler layout, or paste a smaller table built from markdown inside Expand (sometimes accepted when the table UI insert is blocked), or
Link to a child page / excerpt that holds the full table.

If this page was converted from legacy storage format, try “…” → page history / recreate the Expand in a fresh blank page and paste the table in — conversion artifacts sometimes leave nesting permanently broken on that page only. Worth a short feedback ticket too; nested table-in-Expand is a frequent ask.

Mia Tamm _Simpleasyty_

Hi @Tina-Louise Allaire, just curious,

what are you trying to achieve by putting the table inside the Expand?
Is it mainly to keep the page compact / hide the table until it’s needed, or is there another reason? There might be another way to achieve the same result in the new editor.

Thanks

Welcome!

It looks like you're new here. Sign in or register to get started.

Quick Links

Find more posts tagged with

confluence

cloud

confluence-cloud