---
title: "CFT Forge Migration limitation"
canonical: "https://support.covectors.io/space/CCAD/1932492801/CFT%20Forge%20Migration%20limitation"
format: markdown
---
> Macro (toc)

## 1. Panel Rendering Colors and icons - *Firefox Browser related Issue*

If you are viewing pages including Panels Macro 

![Sans titre.png](media://1781b9de-f988-4763-9ab6-1b0dd1fe78c2)

Panel content set in macro body will not be impacted by panel color (set in edit mode). If you added an icon to panel this will not be displayed also. 

| **Normal Rendering** | **Forge based rendering** |
| --- | --- |
| ![image-20260401-144149.png](media://0fd212c0-bc1a-4d52-9afc-b9ab9e7322a3) | ![image-20260401-143947.png](media://e9f5df08-6e39-45d9-bed6-7eeed6afffec) |

## 2. Nested content Rendering

Bodied macros (Tabs, Panels, Expenders) can include other macros within there bodies. This macro nest is still under continuos improvement. 

### 2.1. Firefox Browser - Protection setting blocks rendering nested macros

You may encounter issues when trying to render pages including macros with Firefox protection setting set to ON. 

![image-20260401-150152.png](media://6b83ef49-2619-456a-861c-f5642663af85)

Nested macro may display the following error message as they are rendering within separate iFrames. Security protection feature within Firefox prevent our macro from being able to render and communicate with that nested iFrame. 

![image-20260401-150322.png](media://abeb4904-e19b-4aa4-8c61-da2b09620f43)

### 2.2. Vectors Macros part of Content Formatting Toolkit as nested macros

In case you have a pages where our non bodied macros (ex. Button, Footnote etc.) are included within our bodied macros (Tabs, Expander, Panels), those macros are still considered as rendering via Connect Framework. 

> ℹ️ In order to have those macros rendering correctly with the new version powered by Forge, you can edit the page and the bodied macro presenting an issue. 
> ℹ️ 
> ℹ️ No changes are required (no changes on macro or store page version). Once macro editor displayed this will trigger the update to forge and it will render correctly.

### 2.3. Atlassian Macros Support

Below is the list of must frequent and used Atlassian macros and what result to expect when being nested in our bodied macros

| **Macros** | **Forge** |
| --- | --- |
| Table | Supported |
| Mention | Supported |
| Emoji | Supported |
| Action Item | Supported |
| Status | Supported |
| Code bloc | Supported |
| Panel | Supported |
| Date | Supported |
| Decision | Supported |
| Bullet points | Supported |
| Link | Supported |
| Image | Supported |
| Divider | Supported |
| Quote | Supported |
| Header | Supported |
| Attachment | Supported |
| Attachments | Supported |
| Jira Work Item | Supported |
| Table of Content | <span style="color: #0747a6">Custom Dev*</span> |
| Create with Template | <span style="color: #0747a6">Custom Dev*</span> |
| User Profile | <span style="color: #0747a6">Custom Dev*</span> |
| Include content (Include page) | <span style="color: #0747a6">Custom Dev*</span> |
| Page Properties Summary | <span style="color: #0747a6">Custom Dev*</span> |
| <span style="color: #ff5630">Calendar</span> | Not Supported |
| <span style="color: #ff5630">List multiple spaces</span> | Not Supported |

- **Custom Dev*:** They are Macros that are unsupported but we managed to replicate the same behaviour as the original Atlassian macros. There also might be some limitations involved with the implementation.

## 3. Confluence Pages export to PDF and/or Doc format 

Currently **Button and Percentage macros** are not rendering correctly when exporting page to PDF or DOC format. We are still working closely with Atlassian to find a technical solution to support export of similar macros. 

## :question_mark: What to do if you notice those issues / limitations within your instance

We truly understand how frustrating these issues can be in your instance. We've been collaborating closely with Atlassian to address these and other nesting problems. 

Your support in encouraging Atlassian to prioritize these fixes is invaluable. If you have contacts at Atlassian or a customer success partner, please include them when opening a support ticket in our system. We're here to provide technical details and advocate strongly to help raise the priority of these concerns.

> Macro (ui-button)