-
Bug
-
Resolution: Unresolved
-
Low
-
Minor
-
Issue Summary
When a dynamicContentMacro is present in the Confluence page and it's using the css property break-inside: avoid, to avoid breaking up sections that belong together in an export, the PDF export page will still have elements split up, which some elements may not appear also.
Steps to Reproduce
- Create a Connect app that uses a dynamicContentMacro with HTML code that contains several sections and CSS that uses break-inside: avoid.
- Export to PDF, and notice the behavior.
Example of HTML:
<body>
<section>First section</section>
<section>
This should not be broken up but break to its own page instead
</section>
</body>
Example of CSS:
section {
height: 800px;
border: 2px dotted red;
}
.keep-page {
break-inside: avoid;
}
Expected Results
PDF export file does not break elements.
Actual Results
PDF export file breaks elements into pages, and some sections may not appear.
Workaround
Currently there is no known workaround for this behavior. A workaround will be added here when available