Rich text macros
Rich text macros serve too many use cases to list, allowing the user the work with the regular Confluence editor composing macro bodies using all the rich-text features Confluence has to offer, including nesting other custom and native Confluence macros. The recently-previewed referentiality feature does not and is not seemingly intended to meet these use cases, as has been discussed in on that page.
Inline macros
Another feature available on both server/DC and Connect going back many years. We have several macros which depend on this and would not make sense to have as block macros.
Custom editor
We’ve invested significant time building a custom editor for our macros, providing highly customized and focused user experiences. We have macro features and functionality which cannot be replicated using the basic Forge macro config components.
Ability to determine edit/view mode
This may be covered in the context token mentioned. Additionally please consider the navigator which allows us to detect preview mode.
Content API
At the moment some of the expand options on the content API do not return expected data for Forge macros, specifically the view and styled_view. Connect macros in these views are displayed with the expected HTML, while a Forge macro has an error.
These are the primary blockers for us adopting Forge.
https://ecosystem.atlassian.net/browse/FRGE-216
https://ecosystem.atlassian.net/browse/FRGE-601
https://ecosystem.atlassian.net/browse/FRGE-511