Issue Summary

The Page Properties Report (Content Properties Report) macro renders inconsistent and random font sizes across rows and columns in Confluence Cloud.

The macro's own Preview dialog shows correct, consistent font sizes. However, once published or viewed in edit mode, font sizes vary — the first/title column appears significantly smaller, and some rows render at different sizes than adjacent rows with equivalent content.
This does not occur on Confluence Server with the same macro configuration and content.

Steps to Reproduce

1. Create multiple pages, each containing a Page Properties macro with a table of data. Label all pages with a common label (e.g. "customer").
2. Create a new page and insert a Page Properties Report macro configured with a firstcolumn (e.g. "Customer Name") and multiple headings columns, filtered by the common label.
3. Open the macro settings and view the Preview — observe that all fonts appear consistent across rows and columns.
4. Save/publish the page.
5. View the published page — observe font size inconsistencies across rows and columns (e.g. the first/title column is noticeably smaller than other columns, and some rows have different font sizes than others).
6. Edit the page — observe the same font size inconsistencies in the editor rendering of the macro.

Expected Results

The Page Properties Report macro should render all rows and columns with consistent font sizes in view mode and edit mode, matching what is shown in the macro's Preview dialog and matching the behavior on Confluence Server.

Actual Results

Font sizes are inconsistent and appear random across the macro's rendered table in both view mode and edit mode. The first/title column (configured via the firstcolumn parameter) renders at a significantly smaller font size than other columns, and some rows render at different sizes than adjacent rows despite equivalent source content. The macro Preview shows correct sizing, confirming this is a page-level rendering issue, not a content issue.

Workaround

Currently there is no known workaround for this behavior. A workaround will be added here when available