...
As an added complexity, many behaviours of new/fabric pages are undesirable and inconsistent with the behaviours of legacy pages. Sometimes, you may be forced to use a legacy page to get a feature or behaviour that has not been implemented or does not work in the new/fabric pages. When you are forced to use a legacy page, you should prefer the "Advanced" versions of the macros, but beware that they come with some limitations. For example, if suppose you nest a Confluence Table macro inside of a MultiExcerpt. In that case, then table sorting will not work in the "Advanced" version because the iframe containing the content does not have cannot access to the CSS styling of the containing page and . Confluence's Table macro depends on the CSS styling of the containing page. In such a case, you must choose the simplermore straightforward, but not as performant, "static" macros.
For See Confluence Cloud documentation for information on telling the difference between an old and a new page, see Confluence Cloud documentation.
...
The MultiExcerpt Advanced macros provide you with two different options: inline and block. The following table provides the differences between inline and block macros:
...
There are many variables to consider, so there is no specific limit but . However, if you are approaching 100 includes on a page, you are probably pushing the limits of your web browser, Confluence, and the MultiExcerpt Include macro. If you are approaching 150, you are probably past the limit.
We are currently considering approaches to increase the performance of the MultiExcerpt macro to allow even more includes. However, you may want to reconsider your page design if you use large numbers of includes on a single page, you may want to reconsider your page design.