Issue Summary

Rendering ADF contents it’s limited to native elements and doesn’t support confluence specific extensions, other 3rd party extension, media, mentions, etc.
Components display differently in view (or export_view ) formats.

These are legacy rendering formats that we use for displaying TinyMCE pages (as one example) and are not updated to look like Fabric pages.

Steps to Reproduce

This is an example of the problem with css stylesheet using {{/rest/api/content }}for Cloud Confluence

1. Get the content body isung /rest/api/content and use parameter body.export_view  and for getting style expand=body.export_view.webresource.superbatch.tags.css
2. As a result of this endpoint, they don't see all style - some icons do not appear (It appears that the svg icon is missing from the content), like in attachement

Expected Results

Allowing renders to render their nested content as a modern/Fabric/ViewPage.

Actual Results

As described in steps to reproduce: they don't see all style and some icons do not appear.

Workaround

Custom UI is rendered in IFrame and vendors can use any UI, including the Editor Renderer mentioned above. This would require a change in the application architecture.