Hi, some of our static macros export very simple tables in XHTML storage format using renderModes. It appears the “improved PDF rendered” has supersized the default table header size.
Image comparing PDF rendering of a simple H1 heading and 3 column table edited inside confluence vs one provided by a static macro returning XHTML.
Below is the View Storage Format of the internal confluence table. The EXACT same XHTML is being sent back by the static macro, but rendered differently by the new PDF rendering engine.
Appreciate any help from Atlassian or others familiar with the XHTML storage format and the new PDF exporter on how to get the table heading size fixed/rendering normally again.
<table data-layout="default" ac:local-id="7599f3db-c4d5-4715-a2c8-63c5b557c15a">
<tbody>
<tr>
<th>
<p><strong>table heading 1</strong></p></th>
<th>
<p><strong>table heading 2</strong></p></th>
<th>
<p><strong>table heading 3</strong></p></th></tr>
<tr>
<td>
<p>table row A data 1</p></td>
<td>
<p>table row A data 2</p></td>
<td>
<p>table row A data 3</p></td></tr>
<tr>
<td>
<p>table row B data 1</p></td>
<td>
<p>table row B data 2</p></td>
<td>
<p>table row B data 3</p></td></tr></tbody></table>
PS. For the curious the MS Word export does render both tables exactly the same.
References
https://developer.atlassian.com/cloud/confluence/modules/macro-render-modes/ https://developer.atlassian.com/cloud/confluence/modules/static-content-macro/
Confluence Storage Format | Confluence Data Center and Server 8.4 | Atlassian Documentation