Issue Summary

When a page has a layout (a two-column layout, for example) and some other content after (outside) this layout, the page storage format gets populated so that the layout encompasses all the page content. Then, when Confluence needs to display that content, the ADF conversion will convert it back, moving the content outside of the layout again.

However, if an app calls the api/v2/pages/ with body-format=storage and uses it to display the page content, all the content will be wrongly nested inside the layout. The same happens if they call the content conversion endpoint and convert it to view.

Steps to Reproduce

1. Create a page with 2-column layout
2. Add a table after (outside) the layout
3. Convert it to view using the Get Pages endpoint

Expected Results

The table is un-nested and shown outside of the layout, as the same conversion back happens.

Actual Results

The table is nested in the layout.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available